If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Sluggish keyboard scrolling

VERIFIED FIXED in M18

Status

()

Core
Event Handling
P3
normal
VERIFIED FIXED
18 years ago
16 years ago

People

(Reporter: lee0, Assigned: waqar)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

18 years ago
When using the cursor keys to scroll a web page in the browser, scrolling does
not stop immediately after a key has been released. It instead continues
scrolling slower than expected.

The provided URL is a prime example, but the problem seems to be general over
all web pages.

Updated

18 years ago
Assignee: leger → joki
Component: Browser-General → Event Handling
QA Contact: leger → janc

Comment 1

18 years ago
Updating QA Contact

Updated

18 years ago
Target Milestone: M16

Comment 2

18 years ago
I'm marking this one as works-for-me.  Scrolling, even on Linux and even with
the keyboard, is damn fast these days (2000031516 build).  Actually, the options
to change status seem to be gone in Bugzilla.  Well: WORKSFORME

Comment 3

18 years ago
I'm using the 2000032309 Linux build, and the keyboard scrolling certainly is
sluggish. It's very fast if you use the mouse to drag the scroll bar, or use a
mouse wheel, but when using the keyboard I get exactly the effect that the
original reporter describes.
I think the reason keyboard scrolling is slower is that there is a repaint
triggered for every down-arrow worth of scrolling.  I think the mouse-scrolling
may look at the current mouse position when there are a bunch of mouse events
accumulated.

Perhaps the keyboard scrolling needs to peek ahead in the key event queue or
something (if that's possible)?

Comment 5

18 years ago
Bulk prioritizing bugs for correct milestones.
Target Milestone: M16 → M18
(Reporter)

Comment 6

18 years ago
This problem seems to have just gone away in recent builds.

Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME
Reopening.  I still see this in 2000-04-10-08-M15 Linux mozilla.  It is
dependent on the painting performance on a given page.  Short pages can usually
do a repaint in less than the key repeat time, and then this bug doesn't show
up.  However, for longer pages, such as http://www.w3.org/TR/REC-CSS1 ,  this
bug still occurs.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(Reporter)

Comment 8

18 years ago
My apologies, then general problem has gone away with small/medium sized pages.

However, with the URL given, it is still a problem.

On the big table listed in http:
//www.people.fas.harvard.edu/~dbaron/tests/perftest this seems to be fixed for
scrolling up but not for scrolling down.  Hmmm... it could be a paint
performance quirk...

Comment 10

18 years ago
Waqar, are you still handling linux layout issues?  This seems to be more a 
repainting problem than an event problem.
Assignee: joki → waqar
Status: REOPENED → NEW
(Assignee)

Comment 11

18 years ago
Looking into it
Status: NEW → ASSIGNED
(Assignee)

Comment 12

18 years ago
This bug has been marked "future" because the original netscape engineer working
on this is over-burdened. If you feel this is an error, that you or another
known resource will be working on this bug,or if it blocks your work in some way
-- please attach your concern to the bug for reconsideration.
(Assignee)

Comment 13

18 years ago
I have a fix for this.
(Assignee)

Comment 14

18 years ago
Fix Checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago18 years ago
Resolution: --- → FIXED

Comment 15

17 years ago
Mass update:  changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer

Comment 16

17 years ago
Updating QA Contact.
QA Contact: ckritzer → lorca
Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok

Comment 18

17 years ago
QA contact updated
QA Contact: gerardok → madhur

Comment 19

16 years ago
verified on build 2001-08-06-trunk
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.