Remove skip-if android from the test_ext_shared_workers_mainprocess_disallowed.js once GeckoView non-e10s mode has been removed
Categories
(WebExtensions :: Android, task, P3)
Tracking
(Not tracked)
People
(Reporter: rpl, Unassigned)
References
Details
The WebExtensions xpcshell tests listed in toolkit/components/extensions/test/xpcshell/xpcshell.ini are currently running in e10s mode on Desktop and non-e10s mode on Android,
the head.js file is setting "browser.tabs.remote.autostart" to false here but that is now too late and the C++ layer already decided in which e10s mode to run and changing the pref will not change the e10s mode anymore (more details in this comment on phabricator).
The test_ext_shared_workers_mainprocess_disallowed.js test file is meant to test that creating a moz-extension:// SharedWorker is aborted when Gecko runs in e10s mode and the extension runs in the main process, and so the patch attached to Bug 1642676 is going to land with skip-if = "android"
.
Once GeckoView non-e10s mode is going to be completely deprecated (Bug 1457601) we should be able to make sure that our xpcshell tests listed in xpcshell.ini are running in the same mode across the supported platforms and builds and we should be able to remove the skip-if at that point.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
As part of Bug 1568597 we have introduced the changes needed to allow a SharedWorker registered by an extension to run in the main process if the build does run the extensions in the main process (like currently in GeckoView) and so the test mentioned in comment 0 has been removed.
Description
•