Google Says It is Not Killing Ad Blockers

Doris Richards
June 16, 2019

The latest Chrome release also fixes the FileSystem API implementation that had made it possible for websites to use scripts to detect if a user was using the Incognito Mode.

There are so many reasons why most PC users like to use the Google Chrome browser the most.

They said, "There's been a lot of confusion and misconception around both the motivations and implications of this change, including speculation that these changes were created to prevent or weaken ad blockers, this is absolutely not the goal".

According to Cronin, the changes they implemented were driven by their desire "to keep users safe and give them more visibility and control over the data they're sharing with extensions". It seemed like Google was trying to break all current ad blockers for Google Chrome.

The original Web Request API allowed developers to stop a page from loading while they looked at the page's content to search for ads or other content, and block or modify it as they wished.

That all said, browser makers including courageous and Opera, which rely on Google's Chromium engine, may skip the upcoming API change, according to a report from ZDNet.

Instead, Google's extension team makes a more general claim that one aspect of a powerful API in particular, the content filtering capability of webRequest, poses potential security and privacy problems.

As one of the solutions, Google replaced some parts of the Web Request API with Declarative Net Request API. "This is absolutely not the goal". Some developers have said this will torpedo their ad blocking and privacy extensions. But, this also includes about 42 percent of malicious Chrome extensions.

Additionally, there are supposed performance costs, impacting page load times. For example, uBlock Origin claims that the changes limit the number of adblocking filters to be used to thirty thousand while that extension uses more than ninety thousand filters.

"Instead of Chrome sending all the information about a request to the listening extensions at the time of the request, extensions register rules that tell Chrome what to do if certain types of requests are seen", Vincent said.

Google claims that the WebRequest API requires the Chrome browser to send all the data in network request to the extension, including sensitive data such as photos and emails. In addition to the way the two APIs work, Google also revealed that it has resulted in performance improvements.

Google affirms that the new API doesn't enable extensions to access any sensitive data from Chrome.

Vincent said that Google is planning to "change the rule limit from maximum of 30k rules per extension to a global maximum of 150k rules".

Google grouped the changes in the Chrome codebase in a new set of rules called Manifest V3, which developers had to follow when coding new extensions or updating old ones to work with Chrome's future codebase.

Other reports by Iphone Fresh

Discuss This Article