40068 - click to cancel context menu triggers onmouseup

Status: NEW

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

Description

[Jesse Ruderman]

1. load attachment to bug 39985
2. right-click in the light gray area (some events should come up)
3. with context menu still up, right-click somewhere else in the light gray area

actual result: onmouseup triggers
expected result: no more events trigger

Comment 1

[Sean Richardson]

Yep, this happens using the 2000-05-22-08-M16 nightly binary on WinNT.
http://bugzilla.mozilla.org/showattachment.cgi?attach_id=8919

I'd guess that it would be the responsibility of the context menu code to
fully consume the event that it uses to dismiss the menu, if it is not
to be passed to the objects underlying it.

See bug 15640, "clicking image in content area to close xul popup loads url",
M19, of which this might be a DUP.

Comment 2

[joki (gone)]

Actually I would disagree with the expected results here.  The mousedown is used 
to dismiss the menu and the afterward the mouseup occurs.

However, I would suggest the based on 4.x behavior and based on how the initial 
menu comes up that we should in fact get all the events and that the second 
right click should in fact immediately bring up a new context menu at the new 
location.  Reassigning this to context menu guys.

Comment 3

[Jesse Ruderman]

Ok, *if* the second right-click were to bring up a new content menu, *then* it 
would make sense to trigger onmousedown/onmouseup/onclick events.  In most 
Windows programs, the second right-click does bring up a new context menu.

I still think it doesn't make sense to give only onmouseup if all the click 
does is cancel the menu (which is what mozilla does for both left- and right-
clicks that cancel a context menu).  It should either be a full click or 
nothing.  In most Windows programs, a left-click that cancels a context menu 
also functions as a normal left-click.

Comment 4

[saari (gone)]

Okay, this is one of the many window trasition event bugs.

Comment 5

[ckritzer (gone)]

Mass update:  changing qacontact to [e-mail]

Comment 6

[Sean Richardson]

Since German has decided that clicks that dismiss menus should have no other 
effect (see bug 21390, "Clicking on Widget or link does nothing if menu open"),
the same logic probably caries over to context menus...

Comment 7

[Sean Richardson]

Ah, should have thought of this a minute ago, but the same onmouseup event
is logged if a click in the light gray div dismisses a menubar menu. So this
affects *all* menus.

Comment 8

[Loco]

Updating QA Contact.

Comment 9

[Hixie (not reading bugmail)]

Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.

Comment 10

[Madhur Bhatia]

QA contact updated

Comment 11

[Jesse Ruderman]

See also bug 89923, click to cancel menu counts toward double click.

Comment 12

[Ian Nartowicz]

The desired behaviour documented in bug 66834 comment 77, the onmouseup event
(and the onmousedown event) is correct on windows platforms.  In other words,
the event shouldn't be blocked just because a menu is open.  For Mac and Unix,
the event should be blocked.  I don't have those platforms to test, but it seems
like this may be working correctly?  Or fixed?  Or fixed just on windows?  Or a
duplicate of bugs which were raised later and are being worked on?