Skip to content
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

Closed
newbe36524 opened this issue Jul 17, 2021 · 5 comments
Closed

Migrate to manifest V3 #18

newbe36524 opened this issue Jul 17, 2021 · 5 comments

Comments

@newbe36524
Copy link
Contributor

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/

@mingyaulee
Copy link
Owner

mingyaulee commented Jul 18, 2021

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

  • it is not a standard across browsers (standardisation is underway)
  • the APIs may differ in different browsers (Firefox's implementation is still under development)
  • the browser polyfill does not support the new APIs yet (issue)
  • Background page is deprecated in manifest v3 in favour of service worker, which we can't load Blazor at the moment because Blazor needs a root component to render. In addition, it would have a bad performance impact of we were to use Blazor in service worker because of the lifecycle (where service workers are loaded when needed and unloaded in maximum of 5 minutes)

To workaround the limitations of

  1. APIs not available in the browser polyfill - use JS interop to call to the APIs directly
  2. Service worker - implement service worker fully in JavaScript

@newbe36524
Copy link
Contributor Author

newbe36524 commented Jul 18, 2021

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.
You can close this as you wish.

@mingyaulee
Copy link
Owner

Yeah absolutely, I will add a section in the readme for manifest v3.

@newbe36524
Copy link
Contributor Author

it is about to end of life about manifest v2 https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/

@mingyaulee
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants