He says that the Manifest v3 proposal will take control away from users: “Extensions act on behalf of users, they add capabilities to a user agent, and deprecating the blocking ability of the webRequest API will essentially decrease the level of user agency in Chromium, to the benefit of web sites which obviously would be happy to have the last word in what resources their pages can fetch/execute/render.” Raymond Hill, a developer who has been widely quoted, argues that the changes will kill his uBlock Origin and uMatrix extensions. Some developers have expressed alarm about the impact of the changes on ad blocking and content filtering capabilities of Chrome extensions. We want to make sure all fundamental use cases are still possible with these changes and are working with extension developers to make sure their extensions continue to work while optimizing the extensions platform and better protecting our users.”
Google also provided the following statement to us in email: “These changes are in the design process, as mentioned in Manifest v3 and the Chromium bug. In plain English, Google believes these changes are needed to speed up page load times and make the browser more secure because extensions can both slow down pages and be malicious. It said then that the platform changes “aim to create stronger security, privacy, and performance guarantees.” They will include “more narrowly-scoped and declarative APIs, to decrease the need for overly-broad access and enable more performant implementation by the browser, while preserving important functionality.” Google first discussed the proposed changes in a late 2018 blog post.
The discussion and issues are relatively technical and apply to Chrome extensions generally however, one practical impact would be to disable most ad blockers. According to multiple reports, Google is readying changes to Chromium, which is the software behind the Chrome browser and soon Microsoft Edge.
0 kommentar(er)
