Add a browsingContext getter to the browser element

RESOLVED FIXED in Firefox 65

Status

()

enhancement
P2
normal
RESOLVED FIXED
9 months ago
5 months ago

People

(Reporter: Felipe, Assigned: Felipe)

Tracking

(Blocks 3 bugs)

Trunk
mozilla65
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox64 wontfix, firefox65 fixed)

Details

Attachments

(1 attachment)

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

The test https://searchfox.org/mozilla-central/rev/807a37c670c093b6e5201841a7c5315ba67ba8d5/docshell/test/browser/browser_browsingContext.js 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

Comment 2

7 months ago
Pushed by fgomes@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ab2cc746e451
Add a browsingContext getter to the browser element. r=farre

Comment 3

7 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/ab2cc746e451
Status: ASSIGNED → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
You need to log in before you can comment on or make changes to this bug.