Google’s intent is to make blocking extensions much less flexible and effective, and this method achieves that.

Google’s privacy claim is a canard, extensions still have access to the user’s private data within page. You know better than that Thom, the goal was always about giving google an advantage. I’m concerned with the bean counters and managers, and Google’s omnipresent ad sales managers, who will be all too eager to abuse Chrome’s popularity to make ad blocking harder. I don’t doubt that Google’s Chrome engineers are making these changes because they genuinely believe they make the browser better and safer. We are continuing to iterate on many aspects of the Manifest V3 design, and are working with the developer community to find solutions that both solve the use cases extensions have today and keep our users safe and in control. However, we think it is the right choice to enable users to limit the sensitive data they share with third-parties while giving them the ability to curate their own browsing experience. We understand that these changes will require developers to update the way in which their extensions operate. You can read more about the Declarative Net Request API and how it compares to the Web Request API here. Instead, we want to help developers, including content blockers, write extensions in a way that protects users’ privacy. We are not preventing the development of ad blockers or stopping users from blocking ads. This has been a controversial change since the Web Request API is used by many popular extensions, including ad blockers. Google has written a blog post explaining their reasoning. However, current ad blockers also use the Web Request API currently, and the replacement API limits these extensions in what they can do. Among other changes, the Web Request API will be replaced by the Declarative Net Request API, which is stricter in the kind of data extensions need to function. For a while now, Google has been working on changing the way Chrome extensions work.

Waterfox 32 bit