3 ms·
The 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/blo
by karmelapple 4y ago
The 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.