-
-
Notifications
You must be signed in to change notification settings - Fork 36
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 #18
Comments
You can absolutely implement manifest v3 for your extension, currently there is a validation of the manifest version in the build process but it will be removed soon. Things to be aware of are
To workaround the limitations of
|
It is nice of you to reply to my question, I think there is nothing that needs to be done by this framework but left a link in README.md to indicate this issue. |
Yeah absolutely, I will add a section in the readme for manifest v3. |
it is about to end of life about manifest v2 https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/ |
Yes, unfortunately there is still a lot of work that needs to be done before Blazor can be used in MV3 extensions. At least 2 issues in Chromium that I am aware of: Standardization of web extensions are still underway and it will take some time to get implemented in all the browsers. |
In the Chrome extension store, there is a notice that "Simply migrate to Manifest V3 and enjoy faster auditing services and new APIs and features."
details: https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/
The text was updated successfully, but these errors were encountered: