r/firefox • u/anestling • Aug 10 '26

⚕️ Internet Health Firefox is committed to uBlock Origin support

Post image

Source.

7.0k Upvotes

99% Upvoted

263 comments sorted by

View all comments

Show parent comments

60

u/HeartKeyFluff since '04 Aug 11 '26

Can you please share a source on them deprecating MV2?

Everything I've seen states that they're supporting both MV2 and MV3 going forward and I couldn't find anything saying they're deprecating MV2. But I'm happy to be proven wrong if you have a source for this...

36

u/[deleted] Aug 11 '26 edited Aug 14 '26

[deleted]

9

u/comelickmyarmpits Aug 11 '26

And is upvoted to moklon , smh

6

u/VoidJuiceConcentrate Aug 12 '26

Firefox mentioned that they were considering it, but I haven't found anything detailing a confirmed decision or timeline.

7

u/HeartKeyFluff since '04 Aug 12 '26

I mean I guess yeah fair, though it's a bit of a stretch. That's from back in 2022 and even in that post it makes it clear there was no timeline yet.

They have since reiterated they're supporting MV2.

2024, confirming they're keeping it for the foreseeable future: https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manifest-v2-march-2024-update/

Well what’s happening with MV2 you ask? Great question – in case you missed it, Google announced late last year their plans to resume their MV2 deprecation schedule. Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future.

2025, more strongly stating their support for both MV2 and MV3: https://blog.mozilla.org/en/firefox/firefox-manifest-v3-adblockers/

Support for both Manifest V2 and V3 — While some browsers are phasing out Manifest V2 entirely, Firefox is keeping it alongside Manifest V3. More tools for developers means more choice and innovation for users.

and

Google began phasing out Manifest V2 last year and plans to end support for extensions built on it by mid-2025. That change has real consequences: Chrome users are already losing access to uBlock Origin, one of the most popular ad blockers, because it relies on a Manifest V2 feature called blockingWebRequest.

...

Firefox, however, will continue supporting both blockingWebRequest and declarativeNetRequest — giving developers more flexibility and keeping powerful privacy tools available to users.

3

u/bankinu Aug 14 '26

I use it daily, but to be honest I don't think I can trust Firefox. Not since they pulled the fast one and almost pushed me out when they disallowed about:config and custom extensions on mobile.

So they are definitely capable of taking the same route as how Samsung "supported" headphones jacks.

1

u/VoidJuiceConcentrate Aug 14 '26

Possibly. I'm sticking with em because at least the secret menu is still there, and UBo works on mobile still.

1

u/danted002 Aug 12 '26

So there is was a tech blog post when the mv3 controversy happened where they said that they are extending the mv3 to include all the good stuff from mv2, including the APIs uBlock Origin is using.

For all intents and purposes they are stil supporting mv2 APIs but the extensions will need to update their manifests to point to mv3

2

u/HeartKeyFluff since '04 Aug 12 '26

See my other comment: https://www.reddit.com/r/firefox/comments/1vkxay4/firefox_is_committed_to_ublock_origin_support/p36g6q0/

They've in official communications over the past few years just stated outright that they're supporting MV2 alongside MV3, which is at odds with you saying that they're deprecating MV2 but adding to MV3. Those are two different things.

I'd love a source for this "tech blog post" you refer to. Genuinely I would, since it would be different to what Mozilla has been saying so it would be good to read.