Ad-blocking extensions use the feature to block incoming and outgoing traffic between certain domains and the user’s browser. The web request feature is powerful and flexible, and can be used for both good and bad purposes.
The example provided by Google for Developers shows an extension script that will block the browser from sending traffic to “”: The changes in Manifest V3 are part of a planned overhaul to the specification of Chrome’s browser extension manifest file, which defines permissions, capabilities, and system resources that any extension can use.Ĭurrently under the Active Specification – Manifest V2 – browser extensions can use an API feature called Web Requests to inspect traffic between the browser and the website and to modify or block requests from certain domains. For Google though, sticking with MV3 will have a huge impact on the overall role of ad blocking on the modern web. Although Firefox has a much smaller share of the desktop marketplace than Chrome, this could be a chance for Mozilla’s product to really define itself. Google’s strategy has been roundly criticized by privacy advocates – the Electronic Frontier Foundation has been a vocal opponent – but the search company has not been impressed. But, in a recent blog post, Mozilla clarified that Firefox will retain support for Web Requests, keeping the door open to the most sophisticated forms of ad blocking.įor Google, sticking with MV3 will have a huge impact on the overall role of ad blocking Google has long had security concerns about Web Requests and worked to exclude it from the most recent extension standard, called Manifest v3 or MV3. The breakdown centers on a feature called Web Requests, commonly used in ad blockers and critical to any system that looks to block a domain bulk.
There’s a growing divide over how much space browsers should leave for ad blocking - and Chrome and Firefox have ended up on opposite sides of the battle.
0 kommentar(er)
