Closed Bug 15049 Opened 25 years ago Closed 25 years ago

Nonclient mouse down being handled incorrectly for rollup

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

x86
Other
defect

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.
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.
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?
Duhhhhh? Yes, that sounds like a good idea. I can add a param to the Capture
call.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fixed
Keywords: verifyme
Adding verifyme keyword.
Updating QA Contact.
Component: Browser-General → Event Handling
QA Contact: leger → janc
Mass update:  changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer
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
QA contact updated
QA Contact: gerardok → madhur
verified on build 2001-08-07-08-trunk
Status: RESOLVED → VERIFIED
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.