Manifest v3 extensions are now accepted in the Firefox add-ons store

Hot potatoes: Mozilla has begun accepting Manifest V3 additions to the code signing process for the AMO Store. Starting June 2023, Chrome will only accept MV3 extensions and disabled ad blockers. Mozilla will continue to support full-featured (MV2) ad blockers like uBlock Origin anyway.

Damn day here. Starting today (November 21), extensions created using the controversial Manifest V3 technology will be accepted The official Firefox add-on store (AMO) to sign. Mozilla succumbs to the overwhelming power — and market share — of Google Chrome, though the company has decided to implement its own, more lenient version of MV3.

as such Mozilla Clarified, Manifest V3 is an umbrella term for a number of foundational changes to the WebExtensions API in Fire Fox. The new API was Made by Google as a safer alternative to Manifest V2 for Chrome extensions, but developers have expressed concerns about stricter restrictions that could make ad blockers much less useful than they are today.

Must-have add-ons and add-ons for Firefox digitally signed to appear on the AMO Store, and developers can now begin migrating their code while users of Firefox’s Nightly and Developer Editions can test it. General availability of the MV3 is planned for Firefox 109, release scheduled for January 17, 2023.

Mozilla is working on Provide smooth transitn to MV3 in Firefox, but users and programmers shouldn’t worry. The open source browser will continue to support MV2 extensions “for the foreseeable future”, taking a phased approach and collecting feedback as MV3 matures. Firefox’s implementation of MV3 will differ from other iterations of the technology in two important ways.

First, while other browser vendors have introduced a DNR in favor of web request blocking in MV3, Firefox MV3 continues to support web request blocking and will support a compatible version of DNR in the future. Web request blocking is more flexible than DNR, allowing for more use cases in content blocking (such as ad blockers like the popular uBlock Origin add-on) and other privacy and security extensions.

Furthermore, Firefox’s MV3 presents event pages as text backgrounds instead of service workers. Mozilla states that event pages offer advantages such as the DOM and Web APIs that are not available to service workers, while providing an overall simpler migration path. Event pages (i.e. non-persistent background pages) are more flexible for developers, compared to the Service Workers (scripts that are turned on and then off) alternative that Google proposes.

Source link

Related Posts