-
Notifications
You must be signed in to change notification settings - Fork 17
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
Explore the Manifest V3 #412
Comments
It seems to me that the issue here is understated.
|
@WofWca thanks for context, you're absolutely correct. As i know, this problem is chrome-specific due to nazi policy in their store, firefox still supports v2 manifest. Chrome store have many users, but it never been a main target for Linguist. Altough, to prevent problems in service for users who uses Chrome, we should move to manifest v3. |
Explore manifest v3 features and limitations. If it no limit features that needed for Linguist, we may toggle on v3.
The potential benefits is badges in chrome, that require manifest v3 and comply the best practices. Also, it is possible to use a side panel API.
The text was updated successfully, but these errors were encountered: