You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
@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: