Bypass should-load-in-process checks in window provider when Fission is enabled
Categories
(Core :: DOM: Core & HTML, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: kmag, Assigned: kmag)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
When Fission is enabled, any attempt to load a URI in the wrong process type will automatically be retargeted to the correct process without any special treatment. I'd ideally still like to detect cross-process window.open() calls early and just handle them as remote loads to begin with, but the spec has very definite ideas about how window.open() should behave, and we're expected to return a window with a same-origin about:blank document while the load is pending, so doing so is relatively nontrivial.
Assignee | ||
Comment 1•5 years ago
|
||
When Fission is enabled, the load will be retargeted to the correct process
automatically, and will in the mean time give callers access to an about:blank
document as required by the spec.
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Updated•5 years ago
|
Comment 4•5 years ago
|
||
bugherder |
Comment 5•5 years ago
|
||
Backed out 34 changesets (bug 1561150, bug 1541557, bug 1561724, bug 1561999, bug 1558298, bug 1561061, bug 1532795, bug 1560400, bug 1561122) for beta simulation failures (bug 1563905, bug 1564001):
https://hg.mozilla.org/mozilla-central/rev/7e6657f88b7694ecd841088963ff71d767e4ec22
Comment 6•5 years ago
|
||
Relanded (backout got backed out):
https://hg.mozilla.org/mozilla-central/rev/e596664275d5e3e2fdcb7fa8d1447289f99269c3
Description
•