Aaron Kaluszka Reporter
	Description • 23 years ago

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1+)
Gecko/20010610
BuildID:    2001061020

If a page that has a link to itself is loaded, the multiple loads are not registered

Reproducible: Always
Steps to Reproduce:
1. Load a page
2. Load another page that has a link to itself
3. Hit Back

Actual Results:  You will be taken to the first page

Expected Results:  You should be taken to the same page that you are on

	Claudius Gayle
	Comment 1 • 23 years ago

I've confirmed this with a Mac 0.9.1 build. Confirming and changing OS/Platform
to all/all as this is an XP bug.- i guess it's a bug but I'd like to know under
what circumstance/situation it would be helpful. ps the mozilla.org banner is a
link back to mozilla.org

	Aaron Kaluszka Reporter
	Comment 2 • 23 years ago

Say you are on a page that generates content dynamically: ie. Bugzilla.
Now say you click on a link that effectively refreshes the page.
Now if you want to go back to view the differences between iterations, you can't.
Of course, this may not be a valid example, because of the way caching works,
but its all I could think of right now.

Another oddity:
Go to mozilla.org.
Click on a link.
Click Back
Now click the mozilla.org banner.
Notice Forward is still a valid option which takes you to the link you had
previously clicked.

	Radha on family leave (not reading bugmail)
	Comment 3 • 23 years ago

Not adding the same page to the history is a feature, just like the same page is
not added to global history over and over, no matter how many times you visit
it. each page in history takes up considerable space in memory and is not worth
storing. If a page generates dynamic content, that is the whole idea, (to be
different everytime you visit). If you are talking about a form-post that
submits to itself, there is already a bug for it assigned to (I think) Eric
Pollmann. Otherwise, I don't understand how this will be a useful.

	Aaron Kaluszka Reporter
	Comment 4 • 23 years ago

*** Bug 94737 has been marked as a duplicate of this bug. ***

	Aaron Kaluszka Reporter
	Comment 5 • 23 years ago

REOPENing based on DUPLICATE bug 94737 comments

	Brendan Eich [:brendan]
	Comment 6 • 23 years ago

This bug is more general than described.  Try going to lxr.mozilla.org/mozilla
and typing addRequest into the Identifier search textbox.  Then revise your
search to look for AddRequest.  Go forward to some other page (perhaps by
clicking on one of the links returned by lxr).  Then go back, and you'll see the
first (http://lxr.mozilla.org/mozilla/ident?i=addRequest) results page, not the
second (http://lxr.mozilla.org/mozilla/ident?i=AddRequest).

This bug should be easy to fix, no?  It should not be targeted after mozilla1.0,
I think.

/be

	Brendan Eich [:brendan]
	Comment 7 • 23 years ago

I may be describing a separate bug, where this bug is complaining about the
duplicate suppression.  I'm complaining that the duplicate suppression wrongly
uses strcasecmp, at a guess.  Please file new bug if necessary, or tell me to do
it.  Thanks.

/be

	Radha on family leave (not reading bugmail)
	Comment 8 • 23 years ago

Brendan, for the problem you have described:

Docshell uses nsIURI::Equals()  to determine if 2 urls are the same.
nsIURI::Equals() uses strcasecmp for the same. I will file a bug against necko
for the problem. 

	Nathanael C. Nerode
	Comment 9 • 23 years ago

This bug causes the trouble in bug #136633 because currently view-source uses a
history-entry as its 'web page descriptor'.  View-source should probably use
something better, but there is nothing better.

	Radha on family leave (not reading bugmail)
	Comment 10 • 23 years ago

Moving out, since the bugs that this one depends on is targeted farther than
mozilla 1.0.1 

	Radha on family leave (not reading bugmail)
	Comment 11 • 23 years ago

Re-summarising ...

	Aaron Kaluszka Reporter
	Comment 12 • 23 years ago

Umm the new summary is incorrect.. maybe we need another bug for that specific
problem?

	Brant Gurganus
	Comment 13 • 22 years ago

By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and
<http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss
bugs are of critical or possibly higher severity.  Only changing open bugs to
minimize unnecessary spam.  Keywords to trigger this would be crash, topcrash,
topcrash+, zt4newcrash, dataloss.

	Jesse Ruderman
	Comment 14 • 21 years ago

The case problem is bug 99091.