This API is used by uBlock Origin, AdGuard and many other plugins to block inappropriate content and ensure security. The main dissatisfaction with the third version of the manifest it is related to the transfer to read-only mode of the webRequest API, which allowed you to connect your own controllers that have full access to network requests and can modify traffic on the fly. The main goal of the changes made is to make it easier to build secure, high-performance plugins, and to make it harder to build insecure, slow plugins. The third version of the manifest was developed as part of an initiative to improve plugin security, privacy, and performance. The Chrome manifest defines the capabilities and resources provided by plugins. Initially, the third version of the manifesto was criticized for breaking many plugins to block inappropriate content and ensure security. It is worth mentioning that this change is generated given the changes that will be implemented from January 2023 in Chrome, which plans to stop supporting the second version of the manifest and make the third version mandatory for all plugins. Unlike the classic uBlock Origin, the new plugin uses the capabilities of the built-in engine in the browser to filter content and does not require permission to intercept and change all site data during installation. Raymond Hill, the author of the unwanted content blocking system uBlock Origin, published an experimental uBO Minus browser plugin with an implementation of a variant of uBlock Origin translated to the declarative API NetRequest, whose use is mandatory in the third version of the Chrome manifest. Experimental version only supports network request blocking
0 kommentar(er)
