#110 A switch to Manifest v3
Closed: Fixed 4 months ago by polcak. Opened 2 years ago by polcak.

Summary

We are in the process of migration to MV3. This issue will contain URLs ro resources that we will need during the migration. Please edit this post as wiki.

General

https://extensionworkshop.com/documentation/develop/manifest-v3-migration-guide/#event-driven-background-dscripts

Chromium

https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3.
https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline.

The most important info:

  • In June 2024, Google will start disabling Manifest V2 extensions in pre-stable versions of Chrome (Dev, Canary, and Beta).
  • Chrome 127 will be affected. That means that on Jul 23, Mv3 extension should be unavailable in stable Chromium/Chrome browsers (https://chromiumdash.appspot.com/schedule).

Firefox

https://blog.mozilla.org/addons/2022/10/31/begin-your-mv3-migration-by-implementing-new-features-today/
https://blog.mozilla.org/addons/2022/11/17/manifest-v3-signing-available-november-21-on-firefox-nightly/

Current JShelter status

Giorgio works on NSCL support and observes W3C development. Libor investigates MV3 in general.


https://lists.nongnu.org/archive/html/js-shield/2021-10/msg00026.html:

this is the new scripting API, as currently documented with the features
I and others lobbied for to death:

https://developer.chrome.com/docs/extensions/reference/scripting/

Notice, in particular, the ExecutionWorld and the
RegisteredContentScript types, which allows for unprivileged page
injection and per site/per tab parametrization, respectively.

JShelter 0.19 support Mv3

Metadata Update from @polcak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 months ago

Log in to comment on this ticket.

Metadata