Back in June, Google's Chrome Web Store began alerting users of uBlock Origin who had developer-oriented versions of Chrome that the popular ad-filtering extension could soon stop working.

With the stable release of Chrome 127 on July 23, 2024, the full spectrum of Chrome users could see the warning. One user of the content-blocking add-on [1]filed a GitHub Issue about the notification.

"This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions," the Chrome Web Store (CWS) notification banner explained.

[2]

But Google is being too cautious in its language. uBlock Origin (uBO) will stop working entirely when Google Chrome drops support for Manifest v2 – which uBlock Origin and other extensions rely on to do their thing. When Manifest v2 is no longer supported by Chrome, uBlock Origin won't work at all – that's what Google should be telling users.

You will have to find an alternative to uBO before Google Chrome disables it for good

Raymond Hill, the creator and maintainer of uBO, has made it clear that he will not be trying to adapt uBO to Google's Manifest v3 – the extension architecture that is replacing v2.

"You will have to find an alternative to uBO before Google Chrome disables it for good," he [3]explained in a list of FAQs for uBlock Origin Lite – a content-blocking extension that functions on the upcoming Manifest v3 system but lacks the ability to create custom filters.

[4]

[5]

uBlock Origin Lite, he explained, is "not meant as a [Manifest v3]-compliant version of uBO, it's meant as a reliable Lite version of uBO, suitable for those who used uBO in an install-and-forget manner."

This is a nuanced statement. He's not saying that if you move from uBO to uBlock Origin Lite all will be well and exactly the same – just that uBlock Origin Lite works on Manifest v3, so it will continue working after the v2 purge.

[6]

This nuance is needed because Manifest v2 provided uBlock Origin and other extensions deep access to sites and pages being visited by the user. It allowed adverts and other stuff to be filtered out as desired, whereas v3 pares back that functionality.

While it's difficult to generalize about how the experience of uBO under Manifest v2 and uBOL under Manifest v3 will differ, Hill [7]expects uBOL "will be less effective at dealing with" websites that detect and block content blockers, and at "minimizing website breakage" when stuff is filtered out, because existing uBO filters can't be converted to declarative rules.

Manifest destiny

In 2018 Google [8]announced plans to rewrite the Chrome Extension platform – the set of APIs available to developers of Chrome extension. The legacy scheme, Manifest v2, would be phased out and replaced by Manifest v3.

Manifest v3 curtailed much of [9]the power of the prior extension regime, which could be (and was) easily abused. It did so in the name of security, privacy, and performance – by disallowing, for example, the execution of remotely hosted scripts and requiring that content filtering rules are declared in advance rather than dynamically. (That limitation has [10]eased somewhat .)

[11]Google paying to be default search on phones is totally against antitrust law, judge rules

[12]Firefox's Mozilla follows Google in losing trust in Entrust's TLS certificates

[13]W3C says Google's cookie climbdown 'undermines' a lot of work

[14]Google's plan to drop third-party cookies in Chrome crumbles

One of the consequences of the transition, now supported to varying degrees by other browser makers, is that content blocking and privacy extensions are [15]expected to become less capable due to the limitations of the Manifest v3 APIs.

While Manifest v3's capabilities [16]have been improved in response to feedback – and outfits including AdGuard have expressed [17]cautious optimism – platform improvements haven't made it possible to port uBlock Origin to the new API in a way that retains the desired functionality.

Google has been dropping Manifest v2 support from Chrome gradually [18]since June 2024 in its developer-oriented browser release channels (Canary, Dev, and Beta). But it's still not clear when support will end completely.

[19]

Google didn't immediately respond to a request to clarify when Manifest v2 support will be dropped from the Chrome Stable release channel, but the appearance of a warning banner in the CWS suggests the end is near.

(Enterprise users with managed versions of Chrome have a bit longer, which has led some to contemplate [20]a registry edit to set Chrome's enterprise flag.)

An estimated 34 million people have installed uBO to filter content in Chrome, according to CWS statistics. And a handful of these have already begun making their displeasure known in CWS reviews of the extension.

"As an IT administrator, uBlock Origin is a requirement for our users," wrote one individual posting under the name Kendoka on Monday. "As a personal user, I hereby swear to uninstall Chrome the day ad blockers are removed."

The other ten reviews posted on August 5, 2024 make similar statements. "If or when Chrome kills this extension, I will move to Firefox and never return," wrote someone posting under the name Henry A.

At this point, it's definitely "when," not "if." ®

Get our [21]Tech Resources



[1] https://github.com/uBlockOrigin/uBlock-issues/issues/3309

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZrH0RCU6MzFOUgoNLKTGwAAAANQ&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[3] https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-asked-questions-(FAQ)#will-ubo-automatically-transition-to-ubo-lite-in-the-chrome-web-store

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZrH0RCU6MzFOUgoNLKTGwAAAANQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZrH0RCU6MzFOUgoNLKTGwAAAANQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZrH0RCU6MzFOUgoNLKTGwAAAANQ&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://x.com/gorhill/status/1792688494999155147

[8] https://blog.chromium.org/2018/10/trustworthy-chrome-extensions-by-default.html

[9] https://www.theregister.com/2019/06/17/chrome_extensions_security/

[10] https://developer.chrome.com/blog/improvements-to-content-filtering-in-manifest-v3

[11] https://www.theregister.com/2024/08/05/google_default_search_deals_violate/

[12] https://www.theregister.com/2024/08/01/mozilla_entrust/

[13] https://www.theregister.com/2024/07/30/googles_cookie_w3c_criticism/

[14] https://www.theregister.com/2024/07/23/google_cookies_third_party_continue/

[15] https://www.theregister.com/2022/09/08/ad_blockers_chrome_manifest_v3/

[16] https://developer.chrome.com/blog/extension-news-july-2023

[17] https://www.theregister.com/2023/11/18/google_kills_legacy_extensions/

[18] https://www.theregister.com/2024/05/31/google_prepares_for_chrome_extension/

[19] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZrH0RCU6MzFOUgoNLKTGwAAAANQ&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[20] https://github.com/uBlockOrigin/uBlock-issues/issues/3309#issuecomment-2254334666

[21] https://whitepapers.theregister.com/