`` There is no plan to make changes that limit ad blockers in Firefox, '' Mozilla said clearly


Doug Belshaw

Google is developing version 3 ( Manifest v3 ) of manifest.jason, which is an extension configuration file, and among them, it is criticized as `` I am making changes that restrict the function of the ad blocker '' I was bathing. Meanwhile, Firefox, the second largest share of PC web browsers after Google Chrome, was paying attention to whether or not to follow Manifest v3, but Mozilla's development staff said in the official blog “ About blocking web content I have no plans to follow Manifest v3 . '

Mozilla's Manifest v3 FAQ | Mozilla Add-ons Blog

According to Google's proposed specification, Manifest v3 has deprecated the use of the Web Request API for ad blocking purposes, and a more restrictive new API specification called 'Declarative Net Request API' is recommended. With this API change, the browser Chrome will play the role of removing ads contained in the page content, not the ad blocker extension.

Google Developers Japan: Web Request and Declarative Net Request: How Manifest v3 Affects Extensions

According to Google, processing using the Web Request API is not compatible with Chrome's speedup, and user data may be stolen by malicious extensions. In fact, 42% of malicious extensions seem to have abused the Web Request API, and Google says that the API changes are intended only to improve performance and privacy.

However, because the rules of Declarative Net Request API are very limited, criticism rushed to 'cannot use more complicated ad removal algorithm'. In response to this user response, Google denies that 'There is no purpose to eliminate or weaken ad block extensions in the transition to Manifest v3'.

It turns out that Chrome's `` advertising block disable plan '' is still ongoing-GIGAZINE

On the other hand, the Firefox extension is slightly different from Chrome, but it is basically based on Manifest v2 from the viewpoint of compatibility. Therefore, Chrome and Firefox extensions are easy to port. However, when Chrome migrates to Manifest v3, there is a big difference between Manifest v2 and v3, so the extension of Chrome and Firefox will not keep pace, and developers will have the same extension as Chrome and Firefox Will be difficult to provide to both.

Caitlin Neiman, Mozilla's add-on community manager, said, “If there is no standard for browser extensions, maintaining compatibility with Chrome is important for Firefox developers and users.” 'Firefox is not obligated to implement Chrome's Manifest v3. The Firefox extension is just the foundation, because Manifest v2 makes sense in some parts,' he said.

by Iván Rivera

Mr. Neiman pointed out that 'Manifest v3 is not backward compatible and developers need to adjust the extension', especially for content blocking, 'There is no plan to abolish the Web Request API' Did. On the other hand, Firefox does not follow Manifest v3 at all, and it is planned to implement Manifest v3 partially for the communication specifications.

However, Mr. Neiman said, “The Manifest v3 specification presented by Google is only a draft (draft), and there is a possibility that the contents will change in the future, so what will be changed specifically and how? 'It's too early to say,' so it's possible that Mozilla's policy will change in the future.

in Software, Posted by log1i_yk