Closed
Bug 201591
Opened 22 years ago
Closed 22 years ago
Mouse pointer shape not updated when scrolling with keyboard or mouse wheel
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Core
DOM: UI Events & Focus Handling
Tracking
()
People
(Reporter: vincent-moz, Assigned: saari)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.4b) Gecko/20030315 Build Identifier: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.4b) Gecko/20030315 When one scrolls with the keyboard (arrow keys) or with the mouse wheel, the shape of the mouse pointer never changes, though it sometimes needs to. Reproducible: Always Steps to Reproduce: 1. Put the mouse pointer over a link; its shape is now a hand. 2. Scroll with the keyboard (up arrow or down arrow) or with the mouse wheel in such a way that the mouse pointer is no longer over a link. Actual Results: Nothing except the scrolling: the shape of the mouse pointer is still a hand. Expected Results: The shape of the mouse pointer should have been updated (arrow instead of a hand).
![]() |
||
Comment 1•22 years ago
|
||
Is the hover state updated? We should just be basing the pointer on what's hovered....
Reporter | ||
Comment 2•22 years ago
|
||
When scrolling with the mouse wheel, the hover state is updated (now that bug 78765 has been fixed), but not when scrolling with the keyboard (this is bug 201590).
Comment 3•22 years ago
|
||
-> All/All Win2k/041005 note: this isn't a visible issue on OS X as the moust pointer gets hidden on a page scroll until its moved again.
OS: Linux → All
Hardware: Macintosh → All
Comment 4•22 years ago
|
||
The hover state is not updated, see http://bugzilla.mozilla.org/attachment.cgi?id=47657&action=view for a nice testcase. CONFIRMED, BTW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 5•22 years ago
|
||
*** This bug has been marked as a duplicate of 50511 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•