1610850 - Navigating from about: pages to a web page do not spawn a new BrowsingContext

Status: RESOLVED FIXED

(Core :: DOM: Navigation, defect, P3)

Description

[Alexandre Poirot [:ochameau]]

Let me know if my STR is valid:

• ensure fission is enabled
• open about:robots
• open the browser console
• evaluate gBrowser.selectedBrowser.browsingContext.id to see what is the current BrowsingContext ID.
• navigate to mozilla.org
• re-evaluate gBrowser.selectedBrowser.browsingContext.id and see that the ID did not changed.

The BrowsingContext ID changes when you navigate to about:robots, but not when you navigate from it.

Comment 1

[Chris Peterson [:cpeterson]]

kmag says we want these navigations to create new BrowsingContexts. We should add some tests for these navigations.

Nika asked me to assign this bug to her.

Tracking for Fission riding the trains to Beta (M7)

See Also: → 1602501

Alphan, why is SessionHistory bug 1602501 related to this bug?

Comment 2

[Alphan Chen [:alchen]]

I will remove the see also tag since bug 1602501 does not happen with fission enable.

Comment 3

[Nika Layzell [:nika] (ni? for response)]

Attachment: Bug 1610850 - Part 1: Switch BrowsingContext when navigating parent to remote,

Comment 4

[Nika Layzell [:nika] (ni? for response)]

Attachment: Bug 1610850 - Part 2: Tests for replacing parent process BrowsingContext,

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/42d7139b94be
Part 1: Switch BrowsingContext when navigating parent to remote, r=smaug
https://hg.mozilla.org/integration/autoland/rev/eeb6b2a3ca38
Part 2: Tests for replacing parent process BrowsingContext, r=smaug

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/8c3923411926
Fix lint failure a=lint-fix

Comment 7

[Noemi Erli[:noemi_erli]]

https://hg.mozilla.org/mozilla-central/rev/42d7139b94be
https://hg.mozilla.org/mozilla-central/rev/eeb6b2a3ca38
https://hg.mozilla.org/mozilla-central/rev/8c3923411926