Use process-per-site when in a fission-enabled window
Categories
(Core :: DOM: Content Processes, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
Details
Attachments
(1 file)
We should change the logic to perform process switches on a per-site basis when within a fission-aware window. This will allow us to get an initial implementation of process-per-origin.
|
Assignee | |
Comment 1•5 years ago
|
||
This patch introduces a new type of content process, which has a dynamic name.
This type of content process is labeled as webIsolated=${SITE_ORIGIN} and is
used within fission-enabled windows.
To enable this, additional information about the fission status of the target
window must be passed into E10SUtils. This was done by updating every call site
manually to pass an extra boolean. A better solution perhaps should be used in
the future.
With this patch enabled, we now perform process switches, but only when
navigating to HTTP URIs. If we navigate to a non-HTTP URI in an iframe with
fission enabled, it will not behave correctly. This must be done in a
follow-up.
|
||
Updated•5 years ago
|
Pushed by nlayzell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/7f0dd201e059 Use web processes on a per-site basis for fission-enabled windows, r=mconley
|
|
||
Updated•5 years ago
|
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Description
•