Detect replacement of browsing context for cross-group navigations
Categories
(Remote Protocol :: Marionette, task, P1)
Tracking
(Fission Milestone:M7, firefox85 fixed)
Tracking | Status | |
---|---|---|
firefox85 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [marionette-fission-mvp])
Attachments
(1 file)
Right now we detect remoteness changes when the framescript (listener.js) gets attached:
But once we no longer have the framescript registered, we need a new method in figuring out when the current browsing context gets swapped.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
As given by Olli swapping browsing contexts should actually only happen for top-level browsing contexts. So we could use browsingContext.browserId
to check if the newly created browsing context is related to the currently selected tab.
Comment 2•4 years ago
|
||
Tracking marionette-fission-mvp bugs for Fission Beta milestone (M7).
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
Here actually some details about which objects are placed by a navigation:
https://firefox-source-docs.mozilla.org/dom/navigation/nav_replace.html
So cross-group navigations can actually trigger a replacement of the browsing context .
Assignee | ||
Comment 4•4 years ago
|
||
Also important to note here is that a navigation can be triggered at any time by any command or the website itself. As such this detection should run globally and be active all the time, and not only during a navigation command.
Assignee | ||
Comment 5•4 years ago
|
||
I filed bug 1676709 to get a browsing-context-attached
notification added, which can be used to check if the browsing context was replaced by comparing the browserId
.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 6•4 years ago
|
||
Comment 8•4 years ago
|
||
bugherder |
Updated•2 years ago
|
Description
•