Out-of-process iframes should fire contextmenu events
Categories
(Core :: DOM: Events, defect)
Tracking
()
People
(Reporter: mconley, Unassigned)
References
Details
This is necessary in order to kick off the machinery that actually shows the context menu, which is being built in bug 1505909.
Reporter | ||
Updated•6 years ago
|
Comment 1•6 years ago
|
||
Adding ni for Nika on this as this blocks a M3 frontend task.
Comment 2•6 years ago
|
||
Redirecting to Henri, as this seems related to input events propagating into a content process.
Comment 3•6 years ago
|
||
Opening the context menu by pressing the context menu key on a keyboard that has one opens up the generic page context menu roughly at the right coordinates, but the items in the menu aren't actually contextual to e.g. the text field that the focus is in. (Previously, I thought context menus already worked, because I hadn't paid proper attention to the actual menu items in the menu that shows up.)
As for right-click-initiated context menus, the mouse click itself should be going to the oopif already.
I'm failing to see on Searchfox where these are supposed to connect.
smaug, do you know what mechanism is responsible for deciding that a right click should invoke a context menu?
Reporter | ||
Comment 4•6 years ago
|
||
Gah, this was my fault - it turns out that we are firing the contextmenu event, but my actor wasn't seeing it because it didn't have the allFrames directive in its declaration.
Sorry for the noise. :/
Updated•6 years ago
|
Updated•6 years ago
|
Description
•