Google postpones Chrome content-blocker shakeup once again

The Manifest V3 API continues to be a distant pipe nightmare

When you purchase through links on our site, we may earn an affiliate commission.Here’s how it works.

Googlehasannouncedthat the API for its latest extension platform for Chromium-basedweb browsers, Manifest V3 (MV3), has been delayed once again, with an update from the company expected by March 2023.

The latest development comes just a month before theoriginal January 2023 deadline, announced in early September 2022, was due to take effect. Google seems to be in disarray over the change, as a furtherdelay until January 2024followed in late September, albeit only for enterprise users of Google Chrome.

Extensions are currently built on the Manifest V2 (MV2)  API, which offers robust functionality to developers, allowing effectiveprivacy tools, such as uBlock Origin and Decentraleyes, to flourish. Google is looking to curb that functionality with MV3 by reducing the number of permissions available to developers, which it claims will boost user privacy and performance.

Manifest V3’s privacy implications

Manifest V3’s privacy implications

While Google has longmaintainedthat it intends to support content blocking extensions after the transition, some app developers are finding that this may not end up being the reality.

TechRadar Pro noted in our reporting of the original deadline that core uBlock Origin developer Raymond Hill had developed an MV3-compatible version of the extension, but noted that the functionality was so reduced that there wasn’t “much point” to release.

The Registerhas noted that complaints around functionality and privacy have also come from theElectronic Frontier Foundation, andJean-Paul Schmetz, CEO of privacy suite provider Ghostery, to name but a few.

However, it’s also the case that, perhaps up to now, the transition to MV3 has been happening while the API is an experimental, buggy mess.

Are you a pro? Subscribe to our newsletter

Are you a pro? Subscribe to our newsletter

Sign up to the TechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!

The Registerfound that The Chromium bug report system hasa litany of bugspertaining to it alone, while the new Service Workers function, replacing scripts that run in the background that stop and start as needed, islargely broken, and has been since at least November 2020.

However, it isn’t all bad news: users looking for a trulysecure browsingexperience aren’t out of options just yet.

Google Chrome extensions could pose high security risk, researchers fear>This nasty Google Chrome extension is after your crypto and your passwords>Check out our list of the best business VPNs right now

Alternative browsers built on Chromium, the same underlying engine as Google Chrome, such asMicrosoftEdge, are largely being roped into the change. However, the more privacy-focussedBraveandVivaldiboth have ad and tracker blockers built in that shouldn’t be affected by the move to MV3.

Mozilla Firefox, which claims to be one of the few remaining browsers not built on Chromium, plans to implement MV3 while retaining some of functionality of MV2. AsTechRadar Proreported back in late September, Mozillaintends to keep WebRequest, an API integral to blocking web content and trackers.

ViaThe Register

Luke Hughes holds the role of Staff Writer at TechRadar Pro, producing news, features and deals content across topics ranging from computing to cloud services, cybersecurity, data privacy and business software.

A new form of macOS malware is being used by devious North Korean hackers

Scammers are using fake copyright infringement claims to hack businesses

This super-cheap HP Victus 15 gaming laptop just dropped to its lowest price yet