-
-
Notifications
You must be signed in to change notification settings - Fork 230
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
Upgrade to manifest v3 #238
Comments
I'm interested. I received your reply and am using the plug-in on Firefox in the interim, but would really like to stay with one browser. |
That will be amazing! Thanks for your contribution @MaxterBattle |
Note for the future: https://developer.chrome.com/blog/extension-manifest-converter/ |
Here is a workaround: |
Its just temporary it would work for now as for in 2022 but around mid 2023 or earlier ANY EXTENSION using manifest V2 can't be used on chrome or edge ... i tried to change 3.2.2 manifest code but it ain't workin
|
So I tried to migrate to mv3 (I have it ready), but it's not allowed anymore to create blobs in the background script (which is now a service worker). I am still looking for a solid way around it. As soon as I find it, I'll migrate it. |
Browser vendors, starting with Google, are moving to a policy of not accepting extensions using the older v2 manifest format. Manifest v3 is now mandatory to get on the Chrome web store, and other vendors will follow.
Details on Google's intent with this can be found at https://developer.chrome.com/docs/extensions/mv3/intro/
The conversion involves a conversion to more granular permissions, so that the user can choose which sites the extension will run on, and limit what it can do. I might be able to contribute to an effort to do this. Are you interested?
The text was updated successfully, but these errors were encountered: