Google Could Restrict Modern Ad-Blocking Chrome Extensions to Enterprise Users


The FPS Review
Staff member
May 6, 2019
It may be time to find a new browser. 9to5Google is reporting that Chrome is deprecating the blocking capabilities of the webRequest API, which popular ad blockers rely on to function (blocking ads before they’re downloaded). It will only be available to enterprise deployments.

“Google is essentially saying that Chrome will still have the capability to block unwanted content, but this will be restricted to only paid, enterprise users of Chrome. This is likely to allow enterprise customers to develop in-house Chrome extensions, not for ad blocking usage.”

There’s an alternative system called “declarativeNetRequest” that ad blockers can switch to, but it’s less effective because that method only allows a limit of 30,000 rules. Modern blockers use more than twice that amount.

Google says they’re still trying to work things out.

“Chrome supports the use and development of ad blockers. We’re actively working with the developer community to get feedback and iterate on the design of a privacy-preserving content filtering system that limits the amount of sensitive browser data shared with third parties.”
Not going to lie, I'm guessing an unscheduled meeting with HR is a bigger problem for people who "need" an ad blocker plugin on a work instance of chrome. If I'm on the company hardware or network the only "websites" I'll visit are the intratnet and TFS web portals. Oddly enough I don't need ad blockers for those... But since common sense is anything but common at this point, go ahead and explain how this is the end of times.
If you think about it though, Google is an advertising company. If ad blockers get killed off, then they print more money. That's the same here though - we're working on being ad supported, but it's likely we'll have half or more of our traffic blocking ads. If our ads are relevant and non-obtrusive, then they should be shown, and I think that's the direction that Google is trying to move anyway...
I agree with your stance although I'm concerned advertising distribution is handled by 3rd parties, prime targets for hacking, the number of machines they infiltrate can be huge.
How about a 'Safe Browsing' area on the site informing users how to configure a sandbox/es?
I don't normally block ads but I don't venture into unknown territory much so I should be ok.
Become a Patron!