Fix three xpinstall/browser_enabled* tests with fission
Categories
(Toolkit :: Add-ons Manager, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: zombie, Assigned: zombie)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
[browser_enabled.js]
[browser_enabled2.js]
[browser_enabled3.js]
Actual tests only start after the initial page is loaded, and don't care what was previously in the same tab. Under fission, starting with about:blank involves a process switch, which ContentTask isn't equipped to handle, so just need to avoid that.
|
Assignee | |
Updated•5 years ago
|
|
|
Assignee | |
Comment 1•5 years ago
|
||
|
|
Assignee | |
Comment 2•5 years ago
|
||
[browser_enabled.js]
[browser_enabled2.js]
[browser_enabled3.js]
Pushed by tjovanovic@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1640f6921451 Fix three xpinstall/browser_enabled* tests r=mixedpuppy
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
|
||
Comment 5•5 years ago
|
||
Setting the qe-verify- flag as this is a test related fix.
|
||
Comment 6•5 years ago
|
||
Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission Milestone.
This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:
0ee3c76a-bc79-4eb2-8d12-05dc0b68e732
Description
•