Closed Bug 215090 Opened 22 years ago Closed 12 years ago

scrolling triggered too many times when hitting large resized image

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jmd, Unassigned)

Details

load http://www.nycwireless.net/poe/ scroll to the end, hit page up twice upon the second press, Firebird scrolls up excessively. On my p2 266, it pages up all the way to the top of the page. On another users AMD Athlon XP2000+ it scrolls up "about 25 lines extra" The first rendering of that area takes much longer to display. It's a GIF wiring diagram that's actually a much large images, sized down by the HTML. Note you can trigger this with the arrow keys as well, and also by scrolling down, but pageup is the most noticable. I'm very briefly tapping the key, so somehow the heavy rendering work seems to cause Moz to miss the key release event.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030803 Mozilla Firebird/0.6.1
Component: Browser-General → General
Product: Browser → Firebird
Version: Trunk → unspecified
-> default FB general owners
Assignee: general → blake
Severity: normal → minor
QA Contact: general → asa
In order to help future people confirm this bug, I found it easiest to see when holding either the up or down arrow to scroll. Paging-up caused me to miss the bug entirely (on a 1280x1024 screen). Using the arrow keys shot my CPU usage high enough that XMMS stopped playing briefly.
QA Contact: asa
See also bug #238423: http://bugzilla.mozilla.org/show_bug.cgi?id=238423 That bug is a more general filing of this one and includes a more specific test case (as well as a reference back to this bug).
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a) Gecko/20040425 Firefox/0.8.0+ None of the cases referenced from here cause me any problems. Is this hardware specific?
Assignee: bross2 → nobody
QA Contact: general
I can't reproduce this one anymore in a recent build.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.