{"id":100307,"date":"2021-05-28T16:22:45","date_gmt":"2021-05-28T14:22:45","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/mozilla-obobshhila-plany-po-podderzhke-v-firefox-tretej-versii-manifesta-chrome"},"modified":"2021-05-28T16:22:45","modified_gmt":"2021-05-28T14:22:45","slug":"mozilla-obobshhila-plany-po-podderzhke-v-firefox-tretej-versii-manifesta-chrome","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/mozilla-obobshhila-plany-po-podderzhke-v-firefox-tretej-versii-manifesta-chrome","title":{"rendered":"Mozilla summarized its plans for supporting the third version of the Chrome manifest in Firefox.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Mozilla has released a plan to implement the third version of the Chrome manifest in Firefox, which defines the capabilities and resources available to extensions. The third version of the manifest has faced criticism for disrupting the functionality of many extensions designed for blocking unwanted content and ensuring security. <\/p>\n
Firefox plans to implement nearly all features and limitations of the new manifest, including the declarative API for content filtering (declarativeNetRequest). However, unlike Chrome, Firefox will not discontinue support for the old blocking mode of the webRequest API, at least until the new API fully meets the needs of extension developers using webRequest. This approach will ensure compatibility with Chrome extensions without breaking compatibility with extensions reliant on the webRequest API. <\/p>\n
It is important to note that the main dissatisfaction with the new manifest is related to the transition of the webRequest API to a read-only mode, which previously allowed developers to attach their own handlers with full access to network requests and the ability to modify traffic on the fly. This API is used in uBlock Origin and many other extensions for blocking unwanted content and ensuring security. Instead of the webRequest API, a limited declarativeNetRequest API will be offered, which provides access to a built-in filtering engine that processes blocking rules independently, does not allow the use of custom filtering algorithms, and does not permit the creation of complex overlapping rules depending on conditions. <\/p>\n
Firefox is planning to provide support for the third version of the Chrome manifest for testing at the end of 2021, with the implementation of the new manifest scheduled for early 2022. Key features of the new manifest implementation in Firefox include: <\/p>\n
\n
The provision of the declarativeNetRequest API, while retaining the ability to use the old webRequest API.\n
Changes to Cross-Origin Request Handling \u2014 According to the new manifest, the same authority limitations that apply to the main page will be extended to the content processing scripts that are embedded in it (for example, if the page does not have access to the geolocation API, then the extension script will not receive that access either). Some of the cross-origin request limitation changes are already available for testing in Firefox nightlies (being developed as part of the Fission project, which can be enabled in about:preferences#experimental) and are expected to be widely implemented in the third quarter of 2021.\n
Background pages will be replaced with Service workers operating as background processes. This change is not yet ready for testing.\n
Promise-based API. Firefox already supports this type of API in the 'browser.*' namespace and will move it to the 'chrome.*' namespace for the third version of the manifest.\n
The new granular permission request model \u2014 the extension will not be able to activate for all pages at once (the 'all_urls' permission has been removed), but will operate only in the context of the active tab, meaning the user will need to confirm the extension's function for each site. Mozilla is working on strengthening access control but intends to allow users to make their own decisions about whether to permit extensions to work with different tabs.\n