From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
When smooth-scrolling is enabled, pages don't render correctly when
one pages up in both firefox and thunderbird. What happens is remnants
of the page moving down remain on the screen while the new page
doesn't scroll down to follow the previous page.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Start up firefox
2.Pull up Edit|Preferences|Advanced tab and enable smooth scrolling
3.Page down in a multipage document then page up
I am using an NVidia GeForce4-based card so that might be a factor.
xorg is configured as default save for the NVidia configs (resolution
and using TwinView).
Workaround is to switch off smooth-scrolling, but smooth-scrolling is
a great feature to have in multipage docs for easier visual following.
Oh ... a small change. I just found out it wasn't "Always
reproducible". In fact, I can't seem to produce it right now. If I
figure out what function caused it, I'll update the bugreport.
Okay ... here's an update (and this one's reproducible always so far).
It seems it's not limited to smooth-scrolling at all. Pages don't
refresh properly when paging-up regardless of setting of
smooth-scrolling. It starts to happen when I switch workspaces or I
switch the Firefox/Thunderbird window between Maximized and Resizeable
state. It goes back to being "fixed" when focus leaves the window (but
breaks down again when I do any of the actions I mentioned above).
If you are using the nvidia binary drivers can you switch to open
source nv drivers and see whether this still happens?
Problem persists in FC5 with firefox-1.5-0.5.0.beta1. Font renderer seems
unrelated as both pango and Xft seem affected. Happens on both Open Source
radeon and nv drivers.
This is an excellent page to reproduce this issue.
Since this bugzilla report was filed, there have been several major updates,
which may have resolved this issue. Users who have experienced this problem are
encouraged to upgrade their system to the latest version available. Therefore
closing this bug as obsolete.
If you experience this problem on the up-to-date system, please reopen this bug
with an additional information.