Experiments with extension manifest v3 for Chromium #984
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Jaifroid
force-pushed
the
Extension-manifest-v3
branch
from
7e1461c
to
731ea72
Compare
|
As I have incorporated some innovations and bugfixes from here into master, I have had to rebase and force-push this branch. We are at the stage where we can now fully support Chromium extensions using MV3, with the remote PWA workaround we have already been using for Firefox. The problem will be that we will have to keep supporting MV2 in Firefox because FF hasn't yet enabled the background Service Worker in MV3. But even then, it will only be for the latest browser, so we will have to keep an MV2 version, arguably also for Chromium browsers, as only Chromium >88, or possibly >=90 is supported. |
…x-js into Extension-manifest-v3
|
Ready to be merged, pending decision on #1017. |
|
Code now builds nightly versions of both MV2 and MV3 extensions for Chromium, while building the Firefox extension only as MV2 for now. Until Firefox starts to support Service Workers as background scripts, there is no point trying to change it to MV3 (and especially as there is no shutdown date for MV2 on FF as compared to Chrome). |
This PR is for demonstrating the code used to run a Chromium extension with the webextension manifest v3. See #755. The code is experimental. Not for merging.