[Fission] Audit callers of Document::EnumerateSubDocuments
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
Fission Milestone | MVP |
People
(Reporter: smaug, Assigned: edgar)
References
Details
(Whiteboard: fission-soft-blocker)
Some callers expect to be able to go through all the descendants using recursive calls.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
(In reply to Edgar Chen [:edgar] from comment #1)
I will take a look at this.
Thanks!
Tracking this bug for Fission Milestone MVP for now.
Assignee | ||
Comment 3•3 years ago
|
||
The usage in AutoPrintEventDispatcher::CollectInProcessSubdocuments looks fine, the remote iframe would be handled in BrowserChild::RecvCloneDocumentTreeIntoSelf.
Assignee | ||
Comment 4•3 years ago
|
||
The usage in Document::NotifyLayerManagerRecreated looks fine, the remote iframe would be also handled from BrowserChild::ReinitRendering.
Assignee | ||
Comment 5•3 years ago
|
||
The usage for fullscreen Looks fine.
And there are some tests added for remote iframe, see bug 1665941.
Assignee | ||
Comment 6•3 years ago
•
|
||
The usage in nsHTMLDocument::WillIgnoreCharsetOverride looks fine, as it only cares about the subdocument with same principal.
Assignee | ||
Comment 7•3 years ago
•
|
||
The usage in PresShell.cpp
- FlushThrottledStyles looks fine as this used while handling the event which only cares about the in-process subframes.
- PresShell::SetIsActive looks fine per code comment.
- PresShell::EndPaint looks fine, the remote iframe case would be handled when they getting painted.
- PresShell::Freeze,
the one called from nsDocumentViewer::Destroy probably need to handle the nested in-process case. Then we would need to do the same thing for PresShell::Thaw.
Edit: PresShell::Freeze/Thaw should be good per comment 8.
Comment 8•3 years ago
|
||
I should have put bug 1592895 which is the layout part of auditing.
Assignee | ||
Comment 9•3 years ago
•
|
||
(In reply to Hiroyuki Ikezoe (:hiro) from comment #8)
I should have put bug 1592895 which is the layout part of auditing.
Thanks for this information, the layout part should be good. :)
Assignee | ||
Comment 10•3 years ago
|
||
I think the usages were already audited in bug 1592895 and bug 1656105.
One last thing we need to check is https://searchfox.org/mozilla-central/rev/a166f59fba89fc70ebfab287f4edb8e05ed4f6da/dom/base/Document.cpp#12419-12448 to make sure that the nested in-process case works, e.g. a.com -iframe> b.com -iframe> a.com
.
Assignee | ||
Comment 11•3 years ago
|
||
(In reply to Edgar Chen [:edgar] from comment #10)
I think the usages were already audited in bug 1592895 and bug 1656105.
One last thing we need to check is https://searchfox.org/mozilla-central/rev/a166f59fba89fc70ebfab287f4edb8e05ed4f6da/dom/base/Document.cpp#12419-12448 to make sure that the nested in-process case works, e.g.a.com -iframe> b.com -iframe> a.com
.
bug 1730117 is landed and stuck, I think we could close this now.
Description
•