Closed
Bug 1610850
Opened 5 years ago
Closed 5 years ago
Navigating from about: pages to a web page do not spawn a new BrowsingContext
Categories
(Core :: DOM: Navigation, defect, P3)
Core
DOM: Navigation
Tracking
()
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: ochameau, Assigned: nika)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
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.
Updated•5 years ago
|
Comment 1•5 years ago
|
||
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?
Assignee: nobody → nika
Fission Milestone: --- → M7
Flags: needinfo?(alchen)
Comment 2•5 years ago
|
||
I will remove the see also tag since bug 1602501 does not happen with fission enable.
Flags: needinfo?(alchen)
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Comment 4•5 years ago
|
||
Pushed by nlayzell@mozilla.com:
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
Pushed by nerli@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/8c3923411926
Fix lint failure a=lint-fix
Comment 7•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/42d7139b94be
https://hg.mozilla.org/mozilla-central/rev/eeb6b2a3ca38
https://hg.mozilla.org/mozilla-central/rev/8c3923411926
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox76:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in
before you can comment on or make changes to this bug.
Description
•