contextmenu event (oncontextmenu) does not fire on Shift-Right-Click
Categories
(Core :: DOM: Events, defect, P3)
Tracking
()
People
(Reporter: axenicely, Unassigned)
Details
Updated•7 years ago
|
I'm running into this now and can confirm the same issue for Firefox 67 on OSX 10.14.5
Shift+Right-click, as well as Ctrl+Shift+Left-click since its OSX, will the context menu without firing the contextmenu
event. Both options will fire auxclick
, but without the other event the context menu can't be supressed.
I believe this is a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=897379#c1 and also invalid.
If this isn't a bug, why does shift-right-click behave differently than ctrl-right-click and alt-right-click, which behave as expected? Also, Chrome, Opera, MS Edge, IE 11, and IE 10, all behave as expected. (Also, note that the contextmenu event isn't firing. Even if displaying the context menu were intended, what reason could there be for the event not firing? The most reasonable explanation for all this is that the context menu is being displayed <i>because</i> the event isn't firing.)
Comment 6•4 years ago
|
||
I came here to complain about this bug, but after reading 897379 I understand that this is truly an intended feature and not a bug. Mozilla wants a way for the user to open the context menu no matter what, and they've picked Shift + Right click as the shortcut for this. This means the onContextMenu event is not fired which is unfortunate, but intended.
Updated•3 years ago
|
Comment 7•3 years ago
|
||
Can this be revisited? This is an issue for a remote desktop client like noVNC, where users want to be able to shift-right click their remote applications.
And can Firefox really go against the rest of the browsers here? Our users perceive this as a Firefox bug, since it works in Chrome.
Comment 8•3 years ago
|
||
I'm also not finding the quoted reference (from bug 897379) in the specifications any more. Has this perhaps already been discussed, and Firefox simply not updated?
Comment 9•6 months ago
|
||
Ping!
Could we get a verdict on if this behaviour is still desired? Should this be added as a webcompat issue?
Description
•