back button goes more than one page back and retains top portion of previous page




13 years ago
8 years ago


(Reporter: lgkent, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-11-15])



13 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

When on, when I use back arrow, it goes back more than one page.  Sometimes it goes back to arbitrary earlier pages.  In addition, the top portion of the page I was on persists  (approx. 3 inches), blocking the top portion of any further pages.  The only way to remove this remaining portion of a previous page is to use refresh.

Reproducible: Always

Steps to Reproduce:
1.go to for an item, such as "navy shoes" on an item to get details
4. use back arrow
5. go on to second page of search
6. use back arrow

Actual Results:  
back arrow goes back more than one page.  Part of the image of the product detail stays at the top of all continuing pages

Expected Results:  
go back one page.  No portion of previous pages persists
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.