Open
Bug 1597510
Opened 2 months ago
Updated 2 months ago
Fix uses of nsPrintDialogServiceWin::GetHWNDForDOMWindow in widget/windows/nsPrintDialogWin.cpp
Categories
(Core :: DOM: Navigation, defect, P3)
Core
DOM: Navigation
P3
Tracking
()
NEW
| Fission Milestone | M6 |
People
(Reporter: djvj, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [rm-docshell-tree-item:simple])
In file widget/windows/nsPrintDialogWin.cpp
Gets a DocShell from a window, and obtains the associated tree owner, then the nsIWebBrowserChrome from that, eventually getting the native data and widget.
Seems to be entirely chrome code, everything should be in-process.
Change to using BrowsingContext to walk up the tree, asserting that everything is in process.
|
||
Comment 1•2 months ago
|
||
Kannan says replacing nsIDocShellTreeItem calls should block enabling Fission in Nightly (M6).
Fission Milestone: --- → M6
|
||
Updated•2 months ago
|
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•