492188 - When pressing home key, scrollbar can fail to update position

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Borbus]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.10) Gecko/2009042523 Ubuntu/9.04 (jaunty) Firefox/3.0.10
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.10) Gecko/2009042523 Ubuntu/9.04 (jaunty) Firefox/3.0.10

Sometimes when I press the home key, the page will correctly scroll all of the way up, but the scrollbar will stay in the same position.  It will update when, say, the scroll wheel on the mouse is used.  If the scrollbar is used when it has not updated, the page will immediately scroll down to match the scrollbar.

I have discovered one way to reproduce this, but there may be others.

Reproducible: Always

Steps to Reproduce:
1. Browse to a longish page, scroll right to the bottom (ie. with the end key)
2. Follow a link to another longish page, and scroll to the bottom of that page.
3. Use the back button to return to the previous page, which is correctly scrolled right to the bottom.
4. Now press home to scroll to the top.
Actual Results:  
The page correctly scrolls to the top, but the scrollbar remains in its previous position.

Expected Results:  
The scrollbar should update and move to the top.

Comment 1

[Tyler Downer [He/Him]]

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

Comment 2

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 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.