this post was submitted on 14 Aug 2026
1973 points (99.5% liked)

Technology

87183 readers
2966 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
1973
Firefox is now the last major browser that still supports uBlock Origin (www.pcworld.com)
submitted 2 days ago by mesamunefire@piefed.social to c/technology@lemmy.world
390 comments fedilink hide all child comments
 

Firefox says it will keep supporting uBlock Origin even as Microsoft Edge and other Chromium browsers phase it out under Manifest V3.

you are viewing a single comment's thread
view the rest of the comments
[–] brucethemoose@lemmy.world 9 points 2 days ago* (last edited 2 days ago) (1 children)

First, screw Chrome.

BUT. These headlines are clickbait.

UBO has been disabled in Chrome for a long, long time. This is nothing new. Its old news.

Ublock Lite replaced it, and it’s not going away. It’s inferior and problematic and harder on devs, yes, but unfortunately Chrome users didn’t seem notice.

What’s being disabled is a crazy-difficult-to-enable flag that basically zero Chrome users actually used, and that only (a few) downstream Chromium forks use.

[–] takeda@lemmy.dbzer0.com 1 points 1 day ago* (last edited 1 day ago) (1 children)

Sorry, I didn't use Chrome, which flag?

[–] brucethemoose@lemmy.world 1 points 1 day ago* (last edited 1 day ago) (1 children)

You have to launch Chrome with this command-line argument:

--disable-features=ExtensionManifestV2Unsupported,ExtensionManifestV2Disabled

And then, I think you have to re-enable it with config flags as well:

chrome://flags/#extension-manifest-v2-deprecation-warning         [Disabled]
chrome://flags/#extension-manifest-v2-deprecation-disabled        [Disabled]
chrome://flags/#extension-manifest-v2-deprecation-unsupported     [Disabled]
chrome://flags/#allow-legacy-mv2-extensions                       [Enabled]

I have not tried this personally, though.

[–] takeda@lemmy.dbzer0.com 1 points 1 day ago

Thanks for this.