Closed
Bug 1509021
Opened 6 years ago
Closed 4 years ago
Make it possible to roll back BrowsingContext creation
Categories
(Core :: DOM: Navigation, enhancement, P3)
Core
DOM: Navigation
Tracking
()
RESOLVED
INVALID
| Fission Milestone | Future |
People
(Reporter: farre, Unassigned)
References
(Blocks 1 open bug)
Details
When BrowsingContext::{Create, CreateFromIPC} gets called we send a message to do the corresponding in either the content parent or content child. After that message is sent we should really take care of reverting those actions if we after creating that BrowsingContext fail in such a way that we don't get an nsDocShell that would do that for us.
|
Reporter | |
Updated•6 years ago
|
Blocks: browsingcontext
Priority: -- → P3
|
||
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage 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
Fission Milestone: --- → ?
|
|
||
Updated•4 years ago
|
Fission Milestone: ? → Future
|
|
||
Comment 2•4 years ago
|
||
This bug is not a Fission MVP blocker unless it is breaking some functionality or test.
|
|
Reporter | |
Comment 3•4 years ago
|
||
This isn't an issue any longer I think, when we've re-written how browsing contexts are created and attached.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•