Open
Bug 1587402
Opened 5 years ago
Updated 2 years ago
Audit usage of nsIDocShellTreeItem in nsContentUtils::FlushLayoutForTree
Categories
(Core :: DOM: Navigation, task, P2)
Core
DOM: Navigation
Tracking
()
NEW
Fission Milestone | Future |
People
(Reporter: djvj, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [rm-docshell-tree-item:hard])
This code recursively traverses all children of the current doc-shell tree item, and calls FlushPendingNotifications on it. This does not seem like something that can be synchronized in cross-process state.
Fixing this requires IPC, but probably best implemented by the caller - finding all process-local root documents under the given document (using BrowsingContext) and calling the existing (in-process-only) method.
Reporter | ||
Updated•5 years ago
|
Whiteboard: [rm-docshell-tree-item:hard]
Updated•5 years ago
|
Fission Milestone: --- → M5
Priority: -- → P2
Updated•5 years ago
|
Fission Milestone: M5 → Future
Comment 1•5 years ago
|
||
Kannan says replacing nsIDocShellTreeItem calls should block enabling Fission in Nightly (M6).
Fission Milestone: Future → M6
Updated•5 years ago
|
Summary: Fix usage of nsIDocShellTreeItem in nsContentUtils::FlushLayoutForTree → Audit usage of nsIDocShellTreeItem in nsContentUtils::FlushLayoutForTree
Comment 2•5 years ago
|
||
Auditing whether this use of nsIDocShellTreeItem breaks when Fission is enabled blocks Fission Nightly.
Fission Milestone: M6 → M6b
Updated•4 years ago
|
Type: defect → task
Fission Milestone: M6b → Future
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•