Simply put, instead of extensions doing the network filtering themselves, they would provide a filter list that Chrome itself would parse. One of the proposed changes is a new declarativeNetRequest API, designed to replace the webRequest API that many extensions (including AdBlock Plus and uBlock Origin) currently use. With Manifest V3, currently under development, Google hopes to reduce the possible damage that malicious extensions could do, while also increasing performance and adding new features. Since then, Chrome has been subject time and time again to malicious extensions. While Google hasn't completely backtracked from its plans, it has made concessions amidst public outcry and legal threats.įirst, a bit of backstory - the current API level for Chrome extensions, called 'Manifest V2,' was introduced in 2012.

This isn't something that typical users would have cared much about, until extension developers pointed out that one of the proposed changes could prevent many content blockers (including uBlock Origin) from functioning. Google is currently in the process of updating the API used by Chrome extensions. The webRequest API will still eventually lose its ability to block network requests, under current plans. This post previously stated that Google had completely backtracked on the proposed changes, but that is not true.

Ad blocker google chrome best