Closed Bug 1496840 Opened 5 years ago Closed 5 years ago

Add a browsingContext getter to the browser element


(Core :: DOM: Navigation, enhancement, P2)




Fission Milestone M4
Tracking Status
firefox64 --- wontfix
firefox65 --- fixed


(Reporter: Felipe, Assigned: Felipe)




(1 file)

Right now, the parent process has access to the BrowsingContext tree, but without much information other than the ids.

The test suggests that, right now, the way to find the <browser> -> browsingContext association is to do a round-trip to the content process to ask what is the id of the top-level browsingContext related to that browser.

I imagine this association will directly be available in the parent somewhere in the future (probably not in the front-end), but in the meantime we can have a simple solution to this, similar to how the outerWindowId is already handled.

The main use case is to implement a feature like the Page Info for Fission, which requires information from all child frames, like so:

- get the browsingContext related to this browser
- through it, get the ids of all children browsing contexts
- using the API from bug 1493984 (which uses browsing contexts ids), send a message to all child frames
Priority: -- → P2
Pushed by
Add a browsingContext getter to the browser element. r=farre
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla65

Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission Milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:


Fission Milestone: --- → M4
You need to log in before you can comment on or make changes to this bug.