It seems that when you scroll down a page for a link to render another page from and then select back to go to the original page that was still at the same scroll position you scrolled to, after you mouse click the vertical scroll bar to navigate once again it makes the original page go back to the top instead of staying where you had it scrolled to.
------- Additional Comments From Mike Potter 2002-05-07 18:11 ------- Holy cow, I don't know what that sentence means... Here's what I see: 1. Go to slashdot.org 2. Scroll down. 3. Follow a link. 4. Click back. 5. Notice that the scroll bar is at the top of the page, not where it was when you left the slashdot.org site.
Still occurs in 0.2.8
I believe scrolled position is part of history, although I'm not sure if the responsibility is on Gecko to scroll to it (I would assume so) or on the embedding client app. CC'ing Radha for enlightenment
Assignee: saari → pinkerton
yeah, this is the same as mozdev bug 1048.
Status: NEW → ASSIGNED
The responsibility to scroll to the previous position belongs to Gecko, however session history gives the layout engine the things it needs to scroll to the previous position. I have seen this bug before. This is probably a dupe of something I have. I think the issue with slashdot.org is, it either generates dynamic pages or changes too frequently that gecko can't find the previous location in the page while going back.
*** Bug 148743 has been marked as a duplicate of this bug. ***
Target Milestone: --- → Chimera0.4
*** Bug 150522 has been marked as a duplicate of this bug. ***
*** Bug 151035 has been marked as a duplicate of this bug. ***
http://mozdev.org/bugs/show_bug.cgi?id=1048 is a dupe of this bug.
fwiw, this doesn't always happen. just sometimes.
Summary: Scroll Bar bug → Scrollbar sometimes misplaced going back
*** Bug 151618 has been marked as a duplicate of this bug. ***
*** Bug 152680 has been marked as a duplicate of this bug. ***
*** Bug 152828 has been marked as a duplicate of this bug. ***
*** Bug 153097 has been marked as a duplicate of this bug. ***
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
Awesome... Verified in the 2002-06-21-05 NB.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.