{"id":9077,"date":"2022-11-17T06:00:43","date_gmt":"2022-11-17T14:00:43","guid":{"rendered":"https:\/\/blog.mozilla.org\/addons\/?p=9077"},"modified":"2023-01-12T10:54:35","modified_gmt":"2023-01-12T18:54:35","slug":"manifest-v3-signing-available-november-21-on-firefox-nightly","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/addons\/2022\/11\/17\/manifest-v3-signing-available-november-21-on-firefox-nightly\/","title":{"rendered":"Manifest v3 signing available November 21 on Firefox Nightly"},"content":{"rendered":"

Starting November 21, 2022 add-on developers are welcome to upload their Firefox Manifest version 3 (MV3)<\/a> compatible extensions to addons.mozilla.org<\/i> (AMO) and have them signed as MV3 extensions. Getting an early jump on MV3 signing enables you to begin testing your extension\u2019s future functionality on Nightly to ensure a smooth eventual transition to MV3 in Firefox.<\/p>\n

To be clear, Firefox will continue to support MV2 extensions for the foreseeable future, even as we welcome MV3 extensions in the release to general availability in Firefox 109 (January 17, 2023). Our goal has been to ensure a seamless transition from MV2 to MV3 for extension developers. Taking a gradual approach and gathering feedback as MV3 matures, we anticipate opportunities will emerge over time to modify our initial MV3 offering. In these instances, we intend to take the time necessary to make informed decisions about our approach.<\/p>\n

Towards the end of 2023 \u2014 once we\u2019ve had time to evaluate and assess MV3\u2019s rollout (including identifying important MV2 use cases that will persist into MV3) \u2014 we\u2019ll decide on an appropriate timeframe to deprecate MV2. Once this timeframe is established, we\u2019ll communicate MV2\u2019s closure process with advance notice. For now, please see this guide for supporting both MV2 and MV3 versions of your extension on AMO<\/a>.<\/p>\n

Mozilla\u2019s vision for Firefox MV3<\/h2>\n

Firefox MV3 offers simplified and consolidated APIs, enhanced security and privacy mechanisms, and functionality to better support mobile platforms. As we continue to collaborate with other browser vendors and the developer community to shape MV3, we recognize cross-browser compatibility as a fundamental consideration. That said, we’re also implementing distinct elements to suit Firefox\u2019s product and community needs. We want to give extension developers creative flexibility and choice, while ensuring users maintain access to the highest standards of extension customization and security. Firefox MV3 stands apart from other iterations of MV3 in two critical ways:<\/p>\n

    \n
  1. While other browser vendors introduced declarativeNetRequest (DNR) in favor of blocking Web Request in MV3, Firefox MV3 continues to support blocking Web Request and will support a compatible version of DNR in the future. We believe blocking Web Request is more flexible than DNR, thus allowing for more creative use cases in content blockers and other privacy and security extensions. However, DNR also has important performance and compatibility characteristics we want to support.<\/li>\n
  2. Firefox MV3 offers Event Pages<\/a> as the background script in lieu of service workers, though we plan to support service workers in the future for compatibility. Event Pages offer benefits like DOM and Web APIs that aren\u2019t available to service workers, while also generally providing a simpler migration path.<\/li>\n<\/ol>\n

    Over subsequent releases next year, we\u2019ll continue to expand Firefox MV3 compatibility.<\/p>\n

    MV3 also ushers an exciting user interface change in the form of the new extensions button (already available on Firefox Nightly). This will give users direct control over which extensions can access specific web sites.<\/p>\n

    \"\"

    The extensions button will give Firefox users direct control over website specific extension permissions.<\/p><\/div>\n

    Users are able to review, grant, or revoke MV3 extension access to any website. MV2 extensions will display in the button interface, but permissions access is unavailable. Please see this post for more information about the new extensions button<\/a>.<\/p>\n

    If you\u2019re planning to migrate your MV2 extension to MV3, there are steps you can take today to get started<\/a>. We always encourage feedback from our developer community, so don\u2019t hesitate to get in touch:<\/p>\n