Closed Bug 14565 Opened 26 years ago Closed 26 years ago

Problems Scrolling down using arrow keys in Milestone build 9

Categories

(SeaMonkey :: General, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: crutchmc, Assigned: don)

Details

NOTE: I download the browser about 30 minutes ago, and so I haven't visited a great number of webpages, but I have been able to reproduce these results a couple of times. When viewing a webpage and attempting to use the arrow keys to scroll up/down, the browser usually works, however, there are times when the results are VERY unusual. The following incidents have only occured after resizing the browser windown larger while viewing the same page. Case 1: Page will scroll slowly down the top part of the page, then suddenly skip to the bottom. Pressing up returns you to the position above the skip, and then pressing down again takes you right back to the bottom, skipping a large section of the page. Case 2: Pressing down moves the page down 1 notch, but it immediatly returns back to the top. Holding down the down button causes the screen to shake up/down as it continues to do this. If you scroll down with the mouse in this case, and then press down, you will be returned to the top of the page. Case 3 (this problem is not even trivial, but it is related to the others so I will list it): If you scroll down a page quickly after you make the window larger, the webpage has a tendancy to "flash". It appears that the page is being drawn on the coordinates it would have been before the browser was resized during the intermediate steps, so if there are different colors, it gives the appearance of flashing which can be almost painfull to watch. I hope I have provided enough information about these errors. If not, feel free to e-mail me about it at crutchmc@wam.umd.edu. Sincerely, Michael Crutchfield
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
Michael, thanks for the bug report. Can you try this on a more recent build? I do not see this using a Nov. 1 build on Linux, therefore it may have been fixed. Resolving as worksforme.
Status: RESOLVED → VERIFIED
QA Contact: leger → elig
I'm also unable to reproduce using 1999111909 build on Linux, and am verifying as WORKSFORME. Michael, if you're still seeing this on a current build (e.g. M11 Milestone or M12 daily), could you please re-open this bug report with a reproducible test case? Thanks!
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.