Closed Bug 1553913 Opened 5 years ago Closed 5 years ago

Out-of-process iframes should fire contextmenu events

Categories

(Core :: DOM: Events, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

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.

Fission Milestone: --- → ?

Adding ni for Nika on this as this blocks a M3 frontend task.

Flags: needinfo?(nika)

Redirecting to Henri, as this seems related to input events propagating into a content process.

Flags: needinfo?(nika) → needinfo?(hsivonen)

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?

Flags: needinfo?(hsivonen) → needinfo?(bugs)

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. :/

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
Fission Milestone: ? → ---
Flags: needinfo?(bugs)
You need to log in before you can comment on or make changes to this bug.