For people that may be confused or possibly surprised, although MV3 is a shitty Google thing, Firefox should still implement widely used APIs so developers can still write code once that works on (most) any browser. Having to write a "Firefox specific" Web app or extension would cause friction and limit adoption.
this post was submitted on 15 May 2024
5 points (100.0% liked)
Firefox
17898 readers
104 users here now
A place to discuss the news and latest developments on the open-source browser Firefox
founded 4 years ago
MODERATORS
Manifest v3 is the new cookie replacement in Chrome right? Is Firefox also adopting it? I think Google's version helps them monopolize information collection and inhibit add blocking, I hope Firefox's version doesn't do that? What's the benefit?
Firefox ALSO supports Manifest v3.
What's the benefit?
To make extensions made for Chrome easily portable to Firefox.
Manifest V3 changes capabilities and meta-data about extensions, including limiting lots of things that worsen the experience for AdBlock Users.
Google's "cookie replacement" is Ad Topics, which collects your browser history and puts it into categories, sending those categories to websites.
including limiting lots of things that worsen the experience for AdBlock Users
That is the Chrome implementation; Firefox doesn't and won't impose those limits.
As per the MV3 Specification, it is supposed to remove some APIs.
Firefox included them anyways cuz they're not assholes.
I think there's multiple specifications at this point. There's Chrome describing what they're doing unilaterally, and then there's the WebExtension working group that's trying to get alignment among several browsers.
Manifest v3 is about add-ons or extensions like ad blockers, grease monkey, etc. Manifest v3 gets rid of some features of Manifest v2 that will severely hamper ad blocking. Mozilla has committed to keeping manifest v2 support in addition to v3 as a bypass to this