Google introduced Graph Termination of the second version of the Chrome Manifesta in favor of the third version, which is the object of criticism due to the violation of many additions to block unwanted content and security. Including the second version of the manifesta, the popular Ublock Origin advertising blocker is tied, which cannot be translated into the third version of Manifesta due to the termination of the support of the blocking mode of the API WebRequest.
Starting from January 17, 2022, the CHROME Web Store catalog will stop accepted add-ons using the second version of manifesta, but the developers of previously added add-ons will be able to publish updates. In January 2023, the support of the second version of the manifest will be discontinued in Chrome and all the supplements attached to it will stop working. At the same time, the publication of updates for such additions in Chrome Web Store will be prohibited.
Recall that in the third version of the manifest, which determines the capabilities provided by the additions and resources, in the framework of the security and privacy enhancement initiative instead of the WebRequest Proposed by its capabilities API DeclarativeEnetRequest . While the WebRequest API allows you to connect your own handlers with full access to network queries and modify traffic capable on the fly, the DeclarativeEnetRequest API only provides access to the finite filtering engine built into the browser, independently processing the blocking rule, which does not allow you to use your own filtering algorithms and Not allowing to ask complex rules overlapping each other depending on the conditions.
According to Google’s application, it continues to work on the implementation
In DeclarativeEnetRequest, the opportunities demanded in the add-ons using WebRequest, and intends to bring the new API to the form that fully meets the needs of developers of existing additions. For example, Google has already taken into account Wishes Community and added to the API declarativeEnetRequest support to use several static sets of rules , filtering on regular expressions, modifying HTTP headers, dynamic changes and adding rules, delete and replace request parameters, filtering with binding to tabs and creating specific sets of rules specific sessions. In the coming months, it is additionally planned to implement the support of dynamically customizable content processing scripts and the ability to store data in RAM.