Comment on Chrome’s next weapon in the War on Ad Blockers: Slower extension updates
tigerjerusalem@lemmy.world 10 months ago
Can someone clarify why browsers other than the ones that are Chrome based are forced to adopt Manifest v3?
Can someone clarify why browsers other than the ones that are Chrome based are forced to adopt Manifest v3?
See, that’s the thing: pretty much every browser except Firefox is Chrome-based. When people talk about browsers being forced to accept manifest v3, they’re talking about all the Chrome-based browsers other than Chrome.
why browsers other than the ones that are Chrome based are forced to adopt Manifest v3?
Then the only browser left is Firefox. Edge, Opera, Brave, Vivaldi and a long etc are all Chromium based.
There is also Safari, but Safari does not support WebExtensions in the first place so it does not apply here.
Safari has supported mv2 extensions for years and recently added mv3 support.
However it never supported WebRequest blocking.
Google is the biggest of browser and http/s internet based protocol, so much bigger that everyone plays by googles rules. if they set out manifestv3 the other browsers that are not compatible will not work, and as a result people will abandon them.
ShittyKopper@lemmy.blahaj.zone 9 months ago
They aren’t forced to do anything. Manifest v3 is just a part of the WebExtensions API (which is not a standard and is really just “whatever Chrome does except we ctrl+f’d the word chrome to browser”) which both Safari and Firefox chose to implement in order to make porting of Chrome extensions easier.
Before that, Firefox had a much more powerful extension system that allowed extensions quite a lot of access to browser internals, but that turned out to be a maintenance nightmare so they walled those APIs off (not a coincidence that Firefox started getting massive performance improvements after that, and extensions stopped breaking every other release) and decided to go the WebExtensions route. I have no clue what Safari was up to but I think they implemented it after.
If they don’t implement Manifest v3, extensions that want to work across multiple browsers need to support both the older Manifest v2 and the later Manifest v3, which would be a burden not many extension authors would want to bother with, which would make them just say “yeah we’re not supporting anything outside Chrome”. Firefox avoids this problem by extending the v3 API to allow for the functionality necessary for powerful ad blocking Google removed in v3 (webRequestBlocking) while also implementing the new thing (declarativeNetRequest), so extensions that want to take advantage of the powerful features can do so, while Chrome extensions that are fine with the less powerful alternative can still be ported over relatively easily.
ripcord@kbin.social 9 months ago
Very, very good summary. Thank you.