Not sure if I missed something but as far as I'm aware there is no plan to remove v2 support: https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manif...

And I doubt it will happen but if by some miracle people were switching to Firefox due to v2 phase out in chrome it might send a strong signal to keep supporting it.

I'm already using Manifest V3 in Firefox for a few personal private addons that I develop, and I can confirm that blocking network requests already work perfectly fine in it. The only issues I have with Manifest V3 in Firefox are technical, I haven't noticed any issues that I think are problems of direction.

Firefox's Manifest V3 implementation arguably isn't ready for prime time (it has some pretty egregious bugs), but whenever they finally do get around to dropping Manifest V2 (which I have no idea when that would happen), I'm not really worried about extensions not being able to jump over.

Edge is also ditching Manifest V2 and embracing V3.

This is the extension API change at the heart of the problem.

Any browser based on the Chrome engine has to expend energy to hold to V2 support while embracing the latest engine developments.

https://learn.microsoft.com/en-us/microsoft-edge/extensions-...