We believe that working with other browser vendors in the context of the WECG is the best path toward a healthy ecosystem that balances the needs of its users and developers. This means that support for MV3, by virtue of the combined share of Chromium-based browsers, will be a de facto standard for browser extensions in the foreseeable future. In 2018, Chrome announced Manifest v3, followed by Microsoft adopting Chromium as the base for the new Edge browser. We consider this move to be a long-term success, and we remain committed to the model. Today, many cross-platform extensions require only minimal changes to work across major browsers. By the end of 2017 we had completed that transition and moved completely to the WebExtensions model. We believed then, as we do now, that users would be best served by having useful extensions available for as many browsers as possible. When we decided to move to WebExtensions in 2015, it was a long term bet on cross-browser compatibility. To set the stage, we want to outline the choices we’ve made in adopting MV3 in Firefox, some of the improvements we’re most excited about, and then talk about the ways we’ve chosen to diverge from the model Chrome originally proposed. Today, we’re kicking off our Developer Preview program to gather feedback on our implementation of MV3. We proposed Event Pages in the WECG, which has been welcomed by the community and supported by Apple in Safari.
Since then, it became apparent that numerous use cases would be at risk if this were to proceed as is, so we went back to the drawing board. In our previous update, we announced that we would be supporting MV3 and mentioned Service Workers as a replacement for background pages. A lot has changed since then, not least of which has been the formation of a community group under the W3C to advance cross-browser WebExtensions (WECG). It’s been about a year since our last update regarding Manifest v3.
0 kommentar(er)
