{"id":52212,"date":"2019-11-03T00:00:00","date_gmt":"2019-11-02T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/v-chrome-nachalos-testirovanie-tretej-redaktsii-manifesta-nesovmestimoj-s-ublock-origin"},"modified":"2020-02-18T13:59:53","modified_gmt":"2020-02-18T10:59:53","slug":"v-chrome-nachalos-testirovanie-tretej-redaktsii-manifesta-nesovmestimoj-s-ublock-origin","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-chrome-nachalos-testirovanie-tretej-redaktsii-manifesta-nesovmestimoj-s-ublock-origin","title":{"rendered":"Chrome has begun testing the third version of the manifest, incompatible with uBlock Origin","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Google Inc. the testing has begun<\/a><\/noindex> of the third version of the Chrome manifest, which disrupts<\/a><\/noindex> the operation<\/a><\/noindex> of many add-ons for blocking unwanted content and ensuring security. Support for the new manifest, which defines the capabilities and resources provided to extensions, has been added to experimental builds. Chrome Canary<\/a><\/noindex>.
\nThe new manifest was developed as part of of the<\/a><\/noindex> enhancing the security, privacy, and performance of extensions (the main goal is to simplify the creation of secure and high-performance extensions while complicating the ability to create insecure and slow extensions).<\/p>\n

The manifest is currently in early alpha testing, is not final, and has been added to allow developers to start experimenting and adapting their add-ons.
\nThe activation of the new manifest is expected next year. The timeline for the discontinuation of support for the second version of the manifest is not yet determined.
\n To simplify the migration of extensions to the new manifest, a checklist<\/a><\/noindex>, including changes that developers of extensions should pay attention to, has been prepared.<\/p>\n

Recall that the main<\/a><\/noindex> dissatisfaction<\/a><\/noindex> a new<\/a><\/noindex> the manifest<\/a><\/noindex> is related to the discontinuation of support for blocking mode of the webRequest API, which will be restricted to read-only mode. An exception will be made only for Chrome for Enterprise, where support for the webRequest API will be maintained. Mozilla has decided not to follow the new manifest and to retain full use of the webRequest API in Firefox.<\/p>\n

Instead of the webRequest API, a declarative API is proposed for content filtering in the new manifest. declarativeNetRequest<\/a><\/noindex>. While the webRequest API allowed custom handlers with full access to network requests and capable of modifying traffic on the fly, the new declarativeNetRequest API provides access to a built-in universal filtering engine that processes blocking rules autonomously, does not allow the use of custom filtering algorithms, and prevents the establishment of complex overlapping rules based on conditions. <\/p>\n

The new manifest also introduces other changes affecting compatibility with extensions. Among them:<\/p>\n