For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions.
What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151.



laughs in Firefox/Librewolf
Corpo banned it for compatibility with crap code apparently
No worries, play store-recaptcha is coming for you too!
?
affects mobile the most obviously… but google’s playbook is to basically have forced telemetry always and enforce integrity of their telemetry, and by extension advertising etc.
https://piunikaweb.com/2026/05/07/google-recaptcha-play-services-requirement/ - this just seems like an ok article for it, I did a simple web search and it came up, but others certainly exist if you dislike the source.
Looking forward to when they remove the old options & force PC users to scan reCAPTCHA QRs:
Those sites will be dead to me :)
QR codes are like the popups of days gone by. With incredibly few exceptions, I refuse to scan them. They are so easy to redirect for nefarious purposes, and you can’t easily inspect the url to know, assuming thats something you even do. Also my phone case covers the camera and it’s a bitch to get open so I’m very choosy with what gets camera time.
How are people without phones expected to pass the captcha?
FF support is getting worse and worse though.
Barely any of the sites I use for work support FF.
Laugh all you want but shit is a bit fucked.
Ladybird is our last best hope and its barely a glimmer.
Fun fact: many sites that say that they don’t support firefox lie, their sites usually support it but they never tested it or they deem firefox “less secure” or some bullshit, but with an useragent spoofer, they will work
(Not all sites ofc)
Wait, what sites don’t work in firefox?
Yet to see one.
I’ve answered this so many times.
Banks, my uni, accounting software I use at work.
Its a well acknowledged and much discussed fact that the web is buggy with ff.
Wack. Its usually chrome that shits the bed. Or its because their app cant tolerate an adblocker.
Doesn’t match up with my lived experience. Sorry for your loss.
The MV3 support in firefox is even stricter than in Chrome. I found that chrome will let you sidestep CSP to make an HTTP request. Firefox won’t.
I don’t understand what you found, but firefox still supports the web request blocking API for Mv3 extensions, which is what ublock needs.
I was debugging one of my favourite extensions this week to figure out why it didn’t work on firefox. It hadn’t been updated in years, so something changed in firefox in the last few months.
I assume the Chrome version still works. I’m not installing it.
if it hadn’t been updated in years then it will be an Mv2 extension, irrelevant to discussion of Mv3 strictness.