1748676 - Consider supporting background service workers on builds where the extension child process is disabled

Status: NEW

(WebExtensions :: General, task, P3)

Description

[Luca Greco [:rpl] [:luca] [:lgreco]]

In Gecko builds for GeckoView the extension child process is currently disabled (but with web content running in web child processes).

The service workers are currently not expected to be executed in the parent process, the same used to be true for SharedWorkers, but in https://hg.mozilla.org/mozilla-central/rev/8381d47bee21 we have allowed SharedWorkers registered by the extensions to run in the parent process in build where the extension child process is currently disabled and covered it with a test case.

As part of this bug we should consider if as part of the GeckoView transition from MV2 and MV3:

• we intent to support extensions ServiceWorkers running in the parent process (and in that case cover it with an explicit test case as we did for the SharedWorkers)
• or aim to enable the extension child process on GeckoView first (along with enabling event pages in MV2 extensions and ensuring that the extensions subset supported on Fenix will be using an event page)

Along with GeckoView, Thunderbird is also based on a Gecko build where the extension child process is disabled and so we should also consider its possible transition paths and coordinate with Thunderbird developers on this topic.