Closed
Bug 15049
Opened 26 years ago
Closed 26 years ago
Nonclient mouse down being handled incorrectly for rollup
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: hyatt, Assigned: rods)
Details
(Keywords: verifyme)
When combo boxes or XP menus are open, a click on the nonclient area should
cause them to roll up, but the event should not be consumed.
Example: Open up an XP menu or combo box. Click and hold the mouse down on your
window title bar and drag. You should be able to drag, but right now you can't.
Although the combo box or menu does roll up, the event is consumed when it
should be passed on to the nonclient area.
In other cases, I think the event should be consumed, but not in the nonclient
area case.
Assignee | ||
Comment 1•26 years ago
|
||
Kevin and I looked at this closely. In a native Windows app, when the dropdown
is down, it eats the event on rollup, when the menu is down it does NOT eat the
event. We need to choose one. It is as simple as returning FALSE instead of TRUE
from the rollup code.
Reporter | ||
Comment 2•26 years ago
|
||
What if we added a boolean flag that would allow us to say whether or not we
wanted the event consumed? Then we could make both behave the way they're
supposed to?
Assignee | ||
Comment 3•26 years ago
|
||
Duhhhhh? Yes, that sounds like a good idea. I can add a param to the Capture
call.
Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•26 years ago
|
||
Fixed
Updating QA Contact.
Component: Browser-General → Event Handling
QA Contact: leger → janc
Comment 7•25 years ago
|
||
Mass update: changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer
Comment 9•24 years ago
|
||
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
Updated•6 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
•