Closed
Bug 1436504
Opened 7 years ago
Closed 6 years ago
JS APIs for async communication between DocShells
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1467212
People
(Reporter: jryans, Unassigned)
References
(Blocks 1 open bug)
Details
With Site Isolation, potentially any frame in a document can be in a remote process.
Code that interacts with frames (such as DevTools) needs to be updated to treat each frame as potentially remote. To allow this code conversion to happen in parallel with the DOM work to actually move things to separate processes, we should expose message managers[1] for all frames, even those currently in the same process.
[1]: https://searchfox.org/mozilla-central/rev/84cea84b12145d752e50ddca6be5462c38510e35/dom/base/nsFrameLoader.cpp#3115
Updated•7 years ago
|
Priority: -- → P3
Updated•7 years ago
|
OS: Unspecified → All
Hardware: Unspecified → All
Comment 1•7 years ago
|
||
We probably don't want to do this directly as-is, as this will have significant overhead, creating new compartments for every frame in a document. We'll probably take a different approach which does not require creating many Message Managers.
Morphing this bug into the approach we're more likely to take.
Summary: Create message manager for all frames, including same process → APIs for asynchronous communication with Cross-Process nsDocShells
Updated•7 years ago
|
Summary: APIs for asynchronous communication with Cross-Process nsDocShells → JS APIs for async communication between DocShells
Updated•7 years ago
|
Depends on: browsingcontext
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Component: DOM: Content Processes → DOM
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•