-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to manifest v3 #301
Comments
Deadline seems to be January 2023: https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/ I'm still not sure about the support status in Firefox. |
As of today (2022-05-09), Firefox still doesn't seem to have (good?) support for MV3. I played with using symlinks to create two different source directories, one for Firefox and one for Chrome, which use symlinks to the source files, but it failed and it seems like an issue with Chrome. |
It seems we're also blocked on fregante/webext-dynamic-content-scripts#18 |
According to https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/ the original deadline of Jan 2023 (for disabling MV2 in non-stable channels and removing the Featured Badge) is pushed to an unknown date, probably March 2023 or later. |
The phase out has begun |
I am going to be so pissed off when these extensions stop working. |
Manifest v3 landed in Chromium stable 88 (released on January 2021). It's unclear when v2 will stop working.
We need to be careful about Firefox having support: https://blog.mozilla.org/addons/2021/05/27/manifest-v3-update/
The text was updated successfully, but these errors were encountered: