Extensions will be able to define blocking rules in two ways: during installation, and while running. Google went on to highlight the improvements it has made to the new declarativeNetRequest API since it was first introduced. 'Chrome is deprecating the blocking capabilities of the webRequest API in Manifest V3,' a developer advocate at Google wrote in a forum post, 'not the entire webRequest API (though blocking will still be available to enterprise deployments).' In other words, content blockers will have to move to the new limited API at some point, or they'll stop working for regular people. Google has spent the last few months thinking it over, but for the most part, the company is sticking to its existing plan. Many developers, most notably the creator of uBlock Origin and uMatrix, spoke out against the proposed changes. Instead of extensions doing the network filtering themselves, they would provide a filter list that Chrome itself would parse. The change that received the most (negative) publicity was Google's intention to replace the existing webRequest API, used by every content blocking extension, with a more limited declarativeNetRequest API.

Adblock google chrome extension