Fix usage of nsIDocShellTreeItem in nsDocShell::InternalLoad
Categories
(Core :: DOM: Navigation, defect, P2)
Tracking
()
Fission Milestone | Future |
People
(Reporter: djvj, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [rm-docshell-tree-item:hard])
Two uses, the first is more significant.
Here, InternalLoad gets the parent docshell (any type), and if it exists, gets the document from it and calls TryCancelFrameLoaderInitialization()
on it.
This has to be checked for OOP parent, an if so forwarded to the appropriate process.
This usage is a much simpler fix. It occurs within #ifdef DEBUG
code, retrieves the parent and asserts that it is null. Just needs to be changed to use BrowsingContext tree instead to check existence of a (same-type) parent.
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Kannan says replacing nsIDocShellTreeItem calls should block enabling Fission in Nightly (M6).
Comment 2•5 years ago
|
||
This is only relevant in the in-process case, as we will never be in this situation when across process boundaries. This code is only relevant due to timing of frame loader initialization.
Updated•2 years ago
|
Description
•