Manifest v3 in Firefox: Recap and Next Steps
As a developer of a browser supporting WebExtensionsAPI, the move to v3 is going to add so much complexity.<p>For developers, maintaining browser extensions across browsers with different support for WebExtensionsAPI is going to become a major PITA.<p>Even right now one can not submit a new Chrome extension unless it is v3 so that means that extensions codebases have to be branched out for Firefox and Chrome which was not the case before.<p>The hardest will be on the browser side of things. Supporting both v2 and v3 sides of an already extremely complex API (which is what we plan to do) will be causing a lot of issues.<p>The situation is not good. The lack of standard and unity does not help the web.