1496840 - Add a browsingContext getter to the browser element

Status: RESOLVED FIXED

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

Description

[:Felipe Gomes (needinfo for replies!)]

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

Comment 1

[:Felipe Gomes (needinfo for replies!)]

Attachment: Bug 1496840 - Add a browsingContext getter to the browser element. r=farre

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/ab2cc746e451
Add a browsingContext getter to the browser element. r=farre

Comment 3

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/ab2cc746e451

Comment 4

[Chris Peterson [:cpeterson]]

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:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732