Open Bug 1597429 Opened 5 years ago Updated 2 years ago

Fix uses of nsFrameLoader::TryRemoteBrowserInternal in dom/base/nsFrameLoader.cpp

Categories

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

Product:
Core
Component:
DOM: Navigation
Type:
defect

Tracking

()

Project Flags:
Fission Milestone Future

People

(Reporter: djvj, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [rm-docshell-tree-item:simple])

In file dom/base/nsFrameLoader.cpp

Checks parent docshell item type (for not-chrome)

Gets root item and gets chrome window for it, sets the browser-dom-window for the newly created BrowserParent.

Executed in chrome process only, all internal data being adjusted should be accessible.

Change all uses of nsIDocShellTreeItem references to using BrowsingContext instead.

Kannan says replacing nsIDocShellTreeItem calls should block enabling Fission in Nightly (M6).

Fission Milestone: --- → M6
Priority: -- → P3

As this is parent-process only, we don't need to remove these usages in the M6 timeframe.

Blocks: rmrf-docshell-tree-item
No longer blocks: rm-docshell-tree-item
Fission Milestone: M6 → Future
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.