Google said in the forum post, "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." To give you an idea of how the limit might affect ad blockers, EasyList (the main set of rules that most ad blockers use) currently has around 76,000 rules. The current limit is 30,000 during installation, plus 5,000 while running. 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. To fix this, you don’t have to disable your ad blocker completely, but you need to make sure it’s not active on Outlook’s website. If you have an active ad or pop-up blocker extension, then it might be preventing Outlook from loading properly in Chrome. Many developers, most notably the creator of uBlock Origin and uMatrix, spoke out against the proposed changes. Disable Your Ad Blocker for Outlook’s Website. 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.
0 Comments
Leave a Reply. |