Manifest V3, Google Chrome’s soon-to-be definitive basket of changes to the world of web browser extensions, has been framed by its authors as “a step in the direction of privacy, security, and performance.” But we think these changes are a raw deal for users. We’ve said that since Manifest V3 was...
Well, Firefox will adopt Mv3 in the sense that it will be trivial to port a Chrome extension to Firefox. (Which, yes, they do have to do, because Firefox is too small to sustain enough interest from extension devs.)
However, this does not mean that they will adopt the same controversial limitations or drop currently supported APIs.
It is already the case right now that Firefox supports more APIs than Chrome (e.g. the sidebar API) even though they are compatible with Chrome.
And the most controversial aspect of Mv3 – the limitation of the API used for ad blocking – isn’t even relevant, because Firefox has its own, more powerful API which any reasonable ad blocker will use.
Well, Firefox will adopt Mv3 in the sense that it will be trivial to port a Chrome extension to Firefox. (Which, yes, they do have to do, because Firefox is too small to sustain enough interest from extension devs.)
However, this does not mean that they will adopt the same controversial limitations or drop currently supported APIs.
It is already the case right now that Firefox supports more APIs than Chrome (e.g. the sidebar API) even though they are compatible with Chrome.
And the most controversial aspect of Mv3 – the limitation of the API used for ad blocking – isn’t even relevant, because Firefox has its own, more powerful API which any reasonable ad blocker will use.
Exactly. Pleasing both worlds