User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) This is a random occurrence. This product version loaded yesterday. On large pages, text panel (at washington post, Reuters, bugzilla error report page), the page loads normally. If user scrolls down and stops, the page scrolls normally, then jumps (can happen several times). The jump is a few lines up or down, but makes reading very, very difficult. This has to be new behavior, surely I would have noticed on previous versions had it occurred. At first I attributed this to new elements being loaded, but have seen it after several minutes on one page. Reproducible: Sometimes Steps to Reproduce: 1.goto http://www.spiegel.de/international/world/0,1518,679980,00.html#ref=rss 2.wait 3. Actual Results: page jumped several time. The interval between jumps increases (they get further apart) Expected Results: Page should have stopped after loading (I think). It should move in response to scrolling. With no scrolling, the display shouldn't move randomly up and down. Still better than IE, but not as good as FF 3.0 or so.
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 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
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.