Manifest V3

[sublimator]

See:
https://news.ycombinator.com/item?id=24301638

What's not talked about is how moving the "background" process from a long lived hidden web page to a short lived, event based service worker, breaks the actually useful cases of extensions

[sublimator]

https://blog.chromium.org/2020/12/manifest-v3-now-available-on-m88-beta.html

[sublimator]

There now seems to be new docs:
https://developer.chrome.com/docs/extensions/mv3/intro/

[sublimator]

Related to #1995

[sublimator]

Since September last year, MV2 are now scheduled for obsolescence by January 2022.
Need to go through and test out the functionality we are using and see if it's still supported in MV3.

• Need to determine if/when MV3 (Google's version, with only service workers) will be supported by
  • Mozilla
    • Sent an email with subject "Mozilla MV3 support"
    • Rob Wu (@Rob--W) says Mozilla are looking to support "limited" event pages as per Proposal: Limited Event Pages for MV3 w3c/webextensions#134
  • Apple (Safari)
    • Currently not supported as of a year ago, https://developer.apple.com/forums/thread/650463
      • Same person from Apple have previously interacted with regarding popup bugs and missing apis
      • Tried to LI connect with Apple person (@xeenon)
      • "[timothy] Google is not the only browser shipping MV3. Safari 15.4 will ship MV3
        soon. See [March 17th minutes] (https://github.com/w3c/webextensions/blob/main/_minutes/2022-03-17-wecg.md)
      • Apple have actually implemented support for "limited" event pages as per Proposal: Limited Event Pages for MV3 w3c/webextensions#134 (comment)
  • Samsung Internet ( chromium based so probably, but they have a custom extensions codebase )
    • Sent an email with subject Six Extension "Manifest Version 3" Plans
    • Reply: "We will be supported it from Samsung Internet 17.0 market upgrade(End of April)."
    • Sent them the link to limited event pages: Proposal: Limited Event Pages for MV3 w3c/webextensions#134
• Check if ScriptInjection class still works (injecting <script>{code}</script>) (does not)
  • Dan Isaac is helping (https://github.com/Danisco212/InjectionMV3)
  • https://stackoverflow.com/questions/68583169/content-security-policy-in-manifest-version-3-for-chrome-extension
  • https://bugs.chromium.org/p/chromium/issues/detail?id=1137396
  • Doesn't look like sha-$x or unsafe-inline are any longer valid options for script-src CSP directives
  • https://developer.chrome.com/docs/extensions/reference/scripting/#type-ExecutionWorld