Update your extensions from Manifest V2 to V3 #27
Replies: 4 comments 5 replies
-
How do you respond to concerns from the main uBlock Origin developer (uBlockOrigin/uBlock-issues#338 (comment))? This extension has over 10 mio users on MS Edge and won't work after V3 becomes mandatory. |
Beta Was this translation helpful? Give feedback.
{{title}}
{{editor}}'s edit
{{editor}}'s edit
-
Will MS Edge also kill background service workers every 5 minutes like what Chrome does? Any way to configure the time range or disable it? Updated: I've found https://stackoverflow.com/a/66618269 |
Beta Was this translation helpful? Give feedback.
-
If DOM access is removed, then even Microsoft's own "Microsoft Editor" extension will no longer work. |
Beta Was this translation helpful? Give feedback.
-
The day that the Manifest v3 became required, will be the same one that I change my browser. |
Beta Was this translation helpful? Give feedback.
{{title}}
{{editor}}'s edit
{{editor}}'s edit
-
Microsoft announced the decision to embrace Manifest V3 to help reduce web fragmentation for all developers and enhance privacy, security, and performance for end-users.
From 11 July 2022:
Hidden
orPublic
. Developers must use Manifest V3 to publish new extensions to the Microsoft Edge Add-ons website.Migrating from Manifest V2 to V3 will bring several structural changes to how the browser handles extensions. Manifest V3 is an initiative of the Chromium project.
Here is the link to the official announcement made on Microsoft Edge Insider Tech community
Check out the below resources to learn more about the upcoming changes:
Documentation:
Roadmap:
Microsoft Edge Add-ons Roadmap
Let us know your feedback / challenges in the comments.
Beta Was this translation helpful? Give feedback.
All reactions