Chrome developers listed two reasons behind this new update, one was performance and the other was better privacy guarantee to users. “ We are planning to raise these values but we won’t have updated numbers until we can run performance tests to find a good upper bound that will work across all supported devices.”Īccording to Manifest V3, the declarativeNetRequest API will be treated as the primary content-blocking API in extensions. Although Google claimed that they’re looking to increase this number, they didn’t assure it. Chrome currently imposes a limit of 30,000 rules, However, most popular ad blocking rules lists use almost 75,000 rules. declarativeNetRequest is a less effective, rules-based system. Google developers have introduced an alternative to the webRequest API named the declarativeRequest API, which limits the blocking version of the webRequest API. “Chrome is deprecating the blocking capabilities of the webRequest API in Manifest V3, not the entire webRequest API (though blocking will still be available to enterprise deployments).”
Chrome will still have the capability to block unwanted content, but this will be restricted to only paid, enterprise users of Chrome. Last week, the company shared a statement on Google groups that current ad blocking capabilities will not be changed. Even though Chrome’s Manifest extension system received overwhelmingly negative feedback, Google is standing firm on Chrome’s ad blocking changes. In January, Chrome updated its Manifest V3 extension system that could lead to crippling all ad blockers. 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.
On June 12, Google published a blog post clarifying it’s intentions with ad blocking extension system saying it isn’t trying to kill ad blockers. Update: Opera, Brave, Vivaldi have ignored Chrome’s anti-ad-blocker changes, despite shared codebase.
0 kommentar(er)
