window.open() from content will open non-Fission windows
Categories
(Core :: Window Management, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: kmag, Assigned: u608768)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files, 1 obsolete file)
window.open() from content should always inherit the Fission settings from its caller, but currently relies on window open flags (which we don't respect for content callers, anyway). We need to fix that.
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
Reporter | |
Updated•5 years ago
|
|
||
Updated•5 years ago
|
|
||
Comment 5•5 years ago
|
||
Backed out for Android perma fails.
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=262086802&repo=autoland&lineNumber=3217
Backout: https://hg.mozilla.org/integration/autoland/rev/da953e615472b4f9f5eac5e39bfdf970ba740184
There appears to be some inconsistency between the BrowserHost's load context and the parent DocShell's load context (specifically the UseRemoteTabs() value). Confusingly, this only seems to happen in a few Android WPTs. The updated patch fixes this for the time being with a less-strict failure condition.
|
||
Comment 8•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/7583023fe753
https://hg.mozilla.org/mozilla-central/rev/54f2475b0491
Description
•