Firefox plans to support Manifest V3 because Chrome is the world’s most popular browser, and it wants extensions to be cross-browser compatible, but it has no plans to turn off support for Manifest V2.
If Google decided to break V2 compatibility with V3, Mozilla should announce V4 (or V3 extended), which is V3 but with the missing stuff readded.
That’d be a good practical and great product/tech marketing move. Just like most people won’t see how V3 is worse than V2, V4 will indicate it’s the evolved and improved V3.
It would also simplify supporting V3 and V4 at the same time for extension authors. A great practical gain for extension authors, not having to read and understand two manifest schemes and APIs.
Mozilla’s V3 implementation already extends out removing artificial limitations from it. Mozilla’s doing a reverse E3 and I’m all here for it.
Now if only the nincompoop IT dept on my company allowed me to run Firefox…
::Laughs in Firefox::
Who knows… Firefox might just follow suit. If devs have to write their extensions one for Chrome and once for Firefox, the Firefox one will probably be the first to die.
Isn’t that already how it works? Are there extensions trust work unchanged on both browsers? At the very least they’d have to maintain them on both addon stores.
There’s a common specification called WebExtension, which is used by all modern browsers. Firefox had their own API (XUL/XPCOM) before that, but they deprecated it in 2017. Safari also used to have its own system for extensions, but it’s been deprecated since 2019. The Manifest API is a subset of WebExtension, which defines an extension.
Reminder than most other browsers are based on chromium, and Google can probably break ad blockers on them if they want to.
Brave’s native adblock works better than anything else I’ve tried.
Give Brave a look, folks.
Use Firefox. The crypto bros running Brave have been caught multiple times gathering and selling user data. You use Chrome as the base when you want to hoover data.
False.
They sold data from Brave search, which you don’t have to use. (and I don’t.)
Also, the crypto thing is also opt-in. You don’t have to use it either.
It works better than Firefox, especially if your aim is blocking ads.
“I trust these guys to not sell my data because they’ve only sold me data over there” is a hell of a take.
Someone has their identity tied up in this for some reason
I think that, if you’re going to pretend to know what you’re talking about, you should know what you’re talking about.
I think it’s a good thing that a person as to willingly opt-in to data collection.
It’s really that simple.
They still sold user data without being upfront about it until caught, and are still running a shady-ass business. They’re at the intersection of crypto, bigotry, and dishonesty.
Not using or advocating for Brave is pretty simple.
No thank you, I’ll use Firefox instead. Brendan Eich the CEO of Brave is a POS, he donates to shitty causes and then pretends that those donations don’t define him as a bigot.
“In other words, because he silently donated to causes seeking to strip rights from minority groups instead of directly harassing them, the outrage was unjustified.”
It’s also a chromium based browser so good chance it will loose any ad blocking ability if google decides to play hardball.
I wonder what would happen if µBlockOrigin was just pulled from the Chrome Webstore. Would that drive people to other browsers?
There’s uBO Lite, which is an MV3 version so one step towards making adblockers less useful as Google planned.
Many people have said they have switched already and have said it works without issues (as far as they know). I’m sure there is a huge amount of sites and configs that didn’t make it into the lite version, I guess we’ll find out when a huge userbase refuses to migrate from chrome and installs the uBo-lite
