Closed Bug 1555154 Opened 6 years ago Closed 5 years ago

contextmenu events on main-process XUL documents, like about:preferences, don't cause JS Window Actors to spawn

Categories

(Core :: DOM: Content Processes, defect, P3)

Product:
Core
Component:
DOM: Content Processes
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1581925

People

(Reporter: mconley, Unassigned)

References

Details

In bug 1505909, I'm porting the context menu to be Fission-compatible, and in doing so, noticed that even with the includeChrome WindowActorOptions directive, contextmenu events don't cause the JS Window Actor child to be constructed / handle that event.

I built a small workaround using the old actor system (ContextMenuXULChild.jsm) that will suffice for now until this bug is fixed.

The priority flag is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jmathies)
Flags: needinfo?(jmathies)
Priority: -- → P3

With a little bit of testing, it seems as if the patch from nika in bug 1581925 will fix this, and then we can remove the ContextMenuSpecialProcessChild.jsm workaround.

Depends on: 1581925

Nika landed bug 1581925, and so ContextMenuSpecialProcessChild.jsm isn't needed anymore, and this bug is effectively closed out.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.