Enable MV3 pref everywhere
Categories
(WebExtensions :: General, enhancement, P1)
Tracking
(relnote-firefox 109+, firefox109 fixed)
People
(Reporter: willdurand, Assigned: willdurand)
References
(Blocks 2 open bugs)
Details
(Keywords: dev-doc-complete, Whiteboard: [addons-jira])
Attachments
(1 file)
Like Bug 1789796 but in all channels now \o/
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Pushed by wdurand@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/acc3cfe99446 Enable MV3 by default. r=rpl
Comment 3•1 year ago
|
||
bugherder |
Comment 4•1 year ago
|
||
I'm guessing we'll want to add a relnote for this? Maybe with a link to the blog post?
Assignee | ||
Comment 5•1 year ago
|
||
Yeah, we could do that. What's the process?
Assignee | ||
Comment 6•1 year ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: MV3 is a "big thing" in the WebExtensions ecosystem.
[Affects Firefox for Android]: Yes and no. While the WebExtensions framework is shared between MV2 and MV3, Fenix needs some more work to better support MV3 extensions: it is possible to load MV3 extensions but some UI is missing or not great yet. I’d say, we do not mention MV3 for Firefox for Android yet.
[Suggested wording]: Manifest Version 3 (MV3) is now enabled by default (MV2 remains enabled/supported). This major update also ushers an exciting user interface change in the form of the new Unified Extensions button.
[Links (documentation, blog post, etc)]:
Comment 8•1 year ago
|
||
While this has been documented in the release notes and https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/109 , there are still tasks left. The BCD (and extension workshop?) should be updated so that it is obvious that MV3 is enabled by default.
I just saw this example of a feature that is rendered as unsupported because it is annotated with a flag. I suppose that the flag should be removed and then version_added be bumped to 109: https://github.com/mdn/browser-compat-data/pull/18403#issuecomment-1430467216
The necessary documentation updates are covered by these PRs:
Description
•