Closed Bug 1603724 Opened 5 years ago Closed 4 years ago

WindowContext (or WindowGlobal) needs a reference to the parent WindowContext(Global)

Categories

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

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

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1634764
Project Flags:
Fission Milestone M6

People

(Reporter: zombie, Unassigned)

References

Details

This could be an "XY problem", so here's my usecase X:

  • I get a reference to a WindowGlobalParent in chrome JS, say by receiving a JSWindowActor message from the child process. I need to confirm the origin of that frame (we have documentPrincipal), and that it is same-origin all the way up to the top content frame.

  • I walk up the BC tree, getting the currentWindowGlobal at each step and checking, except those WindowGlobals might not be parents/ancestors of my original frame.

  • If the tab navigated, the whole previous tab containing my original WindowGlobalParent might still be in BFcache, without me being able to detect it.

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

Tracking for Fission Nightly (M6)

Fission Milestone: --- → M6

This method has been added in bug 1634764

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