From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9+) Gecko/20010520 BuildID: 2001052020 when the refresh button is pressed, the page is reloded, and the viewable of the document is reset to the head of the page...which is not the case with IE or Opera. Reproducible: Always Steps to Reproduce: 1. scroll down the page 2. hit refresh Actual Results: viewable area becomes the head of the document Expected Results: the document should refresh but not change the position in the page itself, even if the contet changes. This is the case in IE and Opera There is a package gtk being developed which relies on the position in the document to be maintained in a refresh
Andy, what OS are you testing. I've scrolled down to the bottom of this bug report and hit the reload button and the page scroll position was maintained. Am I misunderstanding your report. tested: 052204 win32 mozilla build on win2K and 052108 linux mozilla build on RH6.2
I tested it on win2k. My initial report neglected to mention that it only occurs when you do a complete refresh (i.e. holding shift and pressing the reload button), but not when you do a standard refresh... sorry! :). This report still stands, as i am unclear as to whether this is the desired behaviour Interestingly enough, if you hold shift and hit f5, this does not happen - nothing seems to happen. But, if you hold ctrl and hit f5, then the page refreshes and the position is reset. I guess that this is a little inconsistent - i.e. it should be either shift or ctrl for both clicking and hitting f5. this shouldn't be in this bug report, but it is kinda related - so it got chucked in (i ill submit a seperate report if that would be helpfull).
OS: All → Windows 2000
confirmed with 052208 mozilla trunk build on win2k. A shift+reloase does not remember scroll position.
Assignee: asa → karnaze
Status: UNCONFIRMED → NEW
Component: Browser-General → Layout
Ever confirmed: true
QA Contact: doronr → petersen
on a 'COMPLETE' refresh, IE doesn't remember its position in the page either. So we behave exactly as IE does in this case. Marking bug as INVALID, this doesnt seem like an issue at all.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.