3 ms·
Would recommend waiting a few weeks for Firefox to ship Manifest V3 because Chrome store isn't accepting new V2 extensions and Mozilla isn't yet accepting V3.
by paulryanrogers 4y ago
Would recommend waiting a few weeks for Firefox to ship Manifest V3 because Chrome store isn't accepting new V2 extensions and Mozilla isn't yet accepting V3.
Firefox MV3 is also a bit different, requiring some swapping / toggling that wasn't needed for MV2.
Worth the pain though as extensions are like magic fairy dust for websites you otherwise cannot control.
- karmelapple 4y agoThe deprecation timelines have been postponed [1] [2]. You can still submit v2… but it’s probably best to build for v3 now. 1. https://developer.chrome.com/blog/more-mv2-transition/ https://developer.chrome.com/blog/more-mv2-transition/ 2. https://groups.google.com/a/chromium.org/g/chromium-extensions/c/zQ77HkGmK9E https://groups.google.com/a/chromium.org/g/chromium-extensio...
- paulryanrogers 4y agoLast week I tried submitting an all new MV2 extension and Chrome Webstore said I had to use MV3. My older extension is still grandfathered in, so I was able to update the pre-existing. So it's awkward until Firefox MV3 is ready.
- karmelapple 4y agoWow, that’s… shocking to me. Thanks for the note!
- fregante 4y agoOnly pre-existing MV2 extensions can be updated. New extensions have had to be MV3 for exactly 12 months already: since January 17th 2022.
- karmelapple 4y agoThanks for the note! I had no idea. And that makes it all the weirder that Google postponed things, especially because it seems the community is relying on Google to provide guidance on how to do a lot of things with MV3.
- r14n 4y agoWould sure be nice if FF was more timely about supporting MV3. The worst part is it looks like they won't be supporting service workers which is what Chrome decided to replace background pages with. Meanwhile devs are stuck maintaining two different versions.