In January 2023, in the test releases of Chrome 112 (Canary, DEV, BETA) an experiment will be conducted on temporary disconnection of support for the second version of the manifesto. In June 2023, the experiment will continue and support for the second version of the manifesto will be disabled in the stable version of Chrome 115. In addition, in January 2023, the third version of the manifesto will become mandatory for the recommended additions in the Chrome Web Store catalog. In June 2023, the Chrome Web Store will be prohibited by publication of publicly affordable additions with the second version of the manifesto, and previously added public additions will be transferred to the Unlisted category. In January 2024, add -ons with the second version of the manifesto will be removed from Chrome Web Store, and a setting will be removed from the browser to return the support of the old manifesto.
Initially, the third version of the manifesto became the object of criticism due to impaired work of many additions to block unwanted content and ensure security, but gradually additions begin to translate to a new manifest, for example, Ublock Origin and Adguard blockers were recently prepared, translated into new Manifesto.
The third version of the manifesto is developed as part of the initiative to strengthen security, confidentiality and complement productivity. The main goal of the changes made is to simplify the creation of safe and high -performance additions, and a complication of the possibility of creating unsafe and slow additions.
The main dissatisfaction with the third version of the manifesto is associated with the transfer of the API webrequest one that allowed their own handlers with complete handlers. Access to network requests and capable of modify traffic on the fly. The specified API is used in UBLOCK Origin, Adguard and many other additions to block unwanted content and security. Instead of the Webrequest API, the third version of the manifest is proposed to the API declaativeNetrequest