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

Explore the Manifest V3 #412

Open
vitonsky opened this issue Feb 28, 2024 · 2 comments
Open

Explore the Manifest V3 #412

vitonsky opened this issue Feb 28, 2024 · 2 comments
Labels
important Must do it RFC Need to triage
Milestone

Comments

@vitonsky
Copy link
Collaborator

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.

@vitonsky vitonsky added the RFC Need to triage label Feb 28, 2024
@WofWca
Copy link

WofWca commented Apr 4, 2024

It seems to me that the issue here is understated.
It's not just about badges. Here's what they say

We will begin disabling Manifest V2 extensions in pre-stable versions of Chrome (Dev, Canary, and Beta) as early as June 2024, in Chrome 127 and later. Users impacted by the rollout will see Manifest V2 extensions automatically disabled in their browser and will no longer be able to install Manifest V2 extensions from the Chrome Web Store.

We expect it will take at least a month to observe and stabilize the changes in pre-stable before expanding the rollout to stable channel

@vitonsky
Copy link
Collaborator Author

vitonsky commented Apr 4, 2024

@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.

@vitonsky vitonsky added the important Must do it label Apr 4, 2024
@vitonsky vitonsky added this to the Next release milestone Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
important Must do it RFC Need to triage
Projects
None yet
Development

No branches or pull requests

2 participants