Closed
Bug 44522
Opened 26 years ago
Closed 26 years ago
Arrows in scrollbars need to behave like normal buttons
Categories
(Core :: XUL, defect, P3)
Tracking
()
Future
People
(Reporter: bugzilla, Assigned: eric)
Details
(Whiteboard: [nsbeta3-])
Build ID: 2000070408
Steps to Reproduce:
(1) Mousedown (left button) on one of the arrows in any scrollbar.
(2) With the left mouse button still down, move the cursor off the arrow.
(3) Move the cursor back over the arrow.
Expected Result: When the cursor moves off of the arrow, the [arrow] button
should return to its normal (non-depressed) state. When the cursor is moved
back over the arrow again, the [arrow] button should depress and scrolling
should continue.
Actual Result: When the cursor is moved off of the arrow, the [arrow] button
stays visually depressed. When the cursor is moved back over the arrow again,
the [arrow] button remains visually depressed, but no scrolling takes place
(you must release the mouse button and re-click on the arrow to continue
scrolling).
| Reporter | ||
Comment 1•26 years ago
|
||
*spam* sorry, didn't mean to designate as enhancement
Severity: enhancement → minor
| Reporter | ||
Comment 2•26 years ago
|
||
John, does your last comment about scrollbarbutton in bug 30384 cover this?
Comment 4•26 years ago
|
||
There are really three issues here (perhaps all three reported previously):
(1) scrolling does not resume on mouseover.
(2) style rules in modern skin need to reflect event change (but classic
picks this change up when moving 'into' the document).
(:hover:active -> :active)
(3) the change in state is not picked up by the event system when moving out
of the window (i.e., in classic skin, the style rule is there, but when
you move from mouseover the button to a point outside the window, that
event is not picked up).
Now to find the duplicates ( 2 may not be reported as such).
| Reporter | ||
Comment 6•26 years ago
|
||
One of these days, in a galaxy far, far away, I'll stop reporting dups. I
don't expect it to be any time soon, though.
*** This bug has been marked as a duplicate of 41577 ***
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•