Partner center will stop accepting new MV2 extensions from 11th July
Hello, Edge Add-ons developers! In May 2022, Microsoft announced the timelines for embracing Manifest Version 3 (MV3) for Microsoft Edge extensions and phasing out support for Manifest Version 2 (MV2). As we move forward in this direction, the following change will come into effect starting 11 th July 2022 – All new extensions must use MV3 to be published to the Microsoft Edge Add-ons store. You can continue updating your existing MV2 extensions that are already published on the Microsoft Edge Add-ons website. This timeline is subject to change; for the latest updates, visit: Overview and timelines for migrating to MV3 Microsoft Edge Add-ons roadmap If you have any technical questions on your MV3 migration or the Microsoft Edge Add-ons ecosystem in general, you can reach out to us via our discussion forum on GitHub. If you are facing any issues on Partner Center, or the Microsoft Edge Add-ons site; or you have any suggestions for us to improve the Microsoft Edge Add-ons ecosystem; you can submit those via our GitHub developer community.New Feature: CORS for extension content scripts | Manifest V3 next phase
It's behind a flag: edge://flags/#cors-for-content-scripts CORS for content scripts Prevent content scripts of Extensions from bypassing CORS. – Mac, Windows #cors-for-content-scripts Microsoft Edge Version 83.0.477.0 (Official build) canary (64-bit) Overview When web pages request cross-origin data with fetch or XHR APIs, the response is denied unless CORS headers allow it. In contrast, extension content scripts have traditionally been able to fetch cross-origin data from any origins listed in their extension's permissions, regardless of the origin that the content script is running within. As part of a broader Extension Manifest V3 effort to improve extension security, privacy, and performance, these cross-origin requests in content scripts will soon be disallowed. Instead, content scripts will be subject to the same request rules as the page they are running within. Extension pages, such as background pages, popups, or options pages, are unaffected by this change and will continue to be allowed to bypass CORS for cross-origin requests as they do today. https://www.chromium.org/Home/chromium-security/extension-content-script-fetches
