s/GetCrossDocParentFrame/GetCrossDocParentFrameInProcess/ in FrameLayerBuilder.cpp
Categories
(Core :: Web Painting, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox88 | --- | fixed |
People
(Reporter: dholbert, Assigned: dholbert)
References
Details
Attachments
(1 file)
|
Bug 1699354: Use "InProcess" version of GetCrossDocParentFrame() in FrameLayerBuilder.cpp. r?mstange
(deleted),
text/x-phabricator-request
|
Details |
Per bug 1698680, we're adding a new wrapper-API called GetCrossDocParentFrameInProcess(), and we're migrating existing GetCrossDocParentFrame() calls to use the new function, after checking that they're OK with the fact that it doesn't cross processes for cross-origin content.
I'm filing this bug to convert the callers in FrameLayerBuilder.cpp.
|
Assignee | |
Comment 1•4 years ago
|
||
This patch doesn't change behavior; it's just switching us between two
functions that do the same thing. (One is literally a trivial wrapper for the
other.)
We're using the new "InProcess" version of this API as a way of annotating
callsites that have been vetted as behaving properly in out-of-process iframes.
The calls in FrameLayerBuilder.cpp seem to be about deciding how best to form
layers from our frame tree. A layer tree and its associated frames will
always be restricted to all live in a particular process, so it's fine
that we're not able to reach other processes when we're making these decisions.
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
|
||
Comment 4•4 years ago
|
||
Setting Fission Milestone to M7a (the current Beta milestone) because this bug is blocking meta bug 1599913 which is a blocker for Fission M7a.
Description
•