Closed Bug 357920 Opened 18 years ago Closed 14 years ago

refresh no re-direct to area of view

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: sethiroth66, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0

looking at a long page will refresh but not how you will expect. looking at an area half way down a page and clicking refresh will re-direct you to the top and not back to the original view you was looking at 

Reproducible: Always
Version: unspecified → 2.0 Branch
I confirm the bug. However, it seems to cause the problem only on dynamically-generated pages, or other pages where content changes. Static pages that return 304 Not Modified when refreshed are correctly scrolled back to where you were. If you scroll down, clear cache and refresh, it will stay on top. Same with Ctrl-F5, etc. Really looks like if page is loaded from cache when refreshing, it immediately scrolls to where you were, but if it reloads from internet, it doesn't.
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.