104777 - Back button goes to incorrect page.

Status: VERIFIED DUPLICATE of bug 103978

(Core :: DOM: Navigation, defect)

Description

[Mark Grosberg]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.5) Gecko/20011011
BuildID:    2001101117

This was observed after using the currently running process for a while to
browse other stuff so who knows if the corruption happend a while ago, but here
is what I saw:


  (1) Went to view how the home-page of the co-location company I use
      looks under Mozilla (http://www.dialtoneinternet.com/)

  (2) That needed Shockwave Flash, so I shut down Mozilla 
      and re-started the process.

  (3) Check my Co-lo's page then check news on Slashdot
      (http://slashdot.org/)

  (4) See what is happening in the world on CNN (http://cnn.com/)

  (5) Clicked link to Taliban story on CNN. Read story and clicked
      back.

After step #5, Mozilla took me to http://www.dialtone.com and the Back button
was disabled as if there was no more history. 

Note: I also had several other browser windows open to various sites
(http://www.weatherundergroun.com [sends cookies]) and my open-source website
(http://www.conman.org/ - pretty vanilla)

Reproducible: Didn't try
Steps to Reproduce:
1. Start browser
2. Goto URL.
3. Enter different URL than in #2 in location bar. 
4. Click link off URL from step #3.
5. Click back. Wrong URL obtained from History.


Actual Results:  The browser disabled the back button (as if there was no
previous history -- and there was) and took me to the wrong spot (arguably the
first URL I typed into the current session).

Expected Results:  Taken me to http://cnn.com since I had previously clicked a
link off that page when I had invoked the Back button.

Comment 1

[Radha on family leave (not reading bugmail)]

THis is probably dupe of another bug I have scheduled for 0.9.6. But would like
to use the steps to reproduce lined out in this bug.

Comment 2

[Radha on family leave (not reading bugmail)]

This is dupe of 103978. Also the problem described here, very similar to 103978
is not reproducible in today's trunk builds. 

*** This bug has been marked as a duplicate of 103978 ***

Comment 3

[Arnoud Berendsen]

v