Closed
Bug 44778
Opened 24 years ago
Closed 24 years ago
[STATE]When mouse is down on a scroll bar, and focus is lost, upon return to mozilla, the scroll bar is still active
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
Future
People
(Reporter: mgoit, Assigned: joki)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt) BuildID: 2000062920 When you have the mouse button selecting a scroll bar, if you lose focus, and the mouse button is still down; upon return the scroll bar is still selected, regardless of mouse button's position. Reproducible: Always Steps to Reproduce: 1. select a scroll bar on the mozilla window 2. lose focus by pressing alt-tab, or by opening a menu (eg right mouse button) 3. lift the mouse button that was selecting the scrollbar 4. return to mozilla 5. move mouse around Actual Results: the scroll bar still reacted to the mouse movement, even though it shouldn't have been affected. Expected Results: The scroll bar should revert to an un-activated state. probably not doing a selected = true or mousebuttonup call, or whatever you called the function when the bar loses focus.
Comment 1•24 years ago
|
||
COnfirmed with 071408 mozilla build on NT. Could reproduce by switching to a different app (not by switching to another mozilla window though) Setting bug status to NEW
Comment 2•24 years ago
|
||
Mass update: changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer
Updated•24 years ago
|
Summary: When mouse is down on a scroll bar, and focus is lost, upon return to mozilla, the scroll bar is still active → [STATE]When mouse is down on a scroll bar, and focus is lost, upon return to mozilla, the scroll bar is still active
Target Milestone: --- → Future
Comment 4•24 years ago
|
||
*** This bug has been marked as a duplicate of 35191 ***
Status: NEW → RESOLVED
Closed: 24 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
•