12/18/2023 0 Comments Adguard mozillaThe organization will implement the declarativeNetRequest API for compatibility reasons according to the blog post. Mozilla will keep the WebRequest API in Firefox to make sure that privacy extensions are not limited in providing the functionality they are designed for. Mozilla notes that the new API limits "capabilities of certain types of privacy extensions without adequate replacement". The decision to remove the blocking part of the WebRequest API and to replace it with the limiting declarativeNetRequest API was at the center of the controversy. A new blog post on the Mozilla Add-ons Community blog sheds light on the adoption and the differences between Mozilla's and Google's implementation. Mozilla announced in 2019 that it would implement support for Manifest V3 in Firefox but would make adjustments to certain limitations. Firefox extensions won't be limited by Manifest V3 The company landed Manifest V3 support in Chrome Canary 80 and in Chrome Beta 88. Google made some concessions to developers but continued its work on introducing the new capabilities and removing the old. Developers voiced concern over some of the planned changes, as they would limit privacy-focused extensions such as content blockers from working properly. The initial version of the draft was discussed controversially. Google announced the new version of the manifest in early 2019 and revealed that Chrome extensions would have to be updated eventually to remain available for users of the Chrome browser. Manifest V3 defines APIs and the capabilities of browser extensions. Content blockers and other privacy extensions will continue to function in Firefox as before, provided that developers continue to support them. While Mozilla plans to introduce support for Manifest V3 in Firefox, it won't remove support for APIs that are essential to privacy extensions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |