Like FLoC and Privacy Sandbox before it, Google Chrome’s Manifest V3 is another example of the inherent conflict of interest that comes from Google controlling both the dominant web browser and one of the largest internet advertising networks.
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