The new set of rules, dubbed Manifest V3, removed APIs such as the blocking version of webRequest – for intercepting and altering the content on web pages before display – and background pages – to handle code listening for specific events.Īn outcry followed from advocacy groups and developers whose extensions depended on Manifest V2 APIs – particularly content blocking, privacy, and scripting extensions – and their objections have yet to be fully addressed. Software developer Jeff Johnson, who runs the Underpass App Company, quipped, "Apple will release its headset as soon as Google transitions to Chrome Extension Manifest V3." We will provide sufficient migration time for developers – at least six months of heads-up – before beginning any experiments to turn off MV2 in the browser next year." "We're still working on the timeline of the MV2 phase-out plan, so keep an eye out for it in the coming months. "We plan to continue reviewing feedback, making changes and improving documentation to ensure the transition from Manifest V2 to Manifest V3 is smooth and successful," the Chrome Extension team told extension developers in a mailing list message. Google, meanwhile, is keen to kill off version 2, and push extensions to V3 of the API. Netizens may want to hold onto their V2 extensions for longer if it means being able to get the most out of the add-ons. Google argues V3 does a better job of protecting users' privacy and security. According to some of the add-ons' developers, V3 limits the effectiveness of the extensions. ![]() Version 3 changes the way ad blockers and other content-filtering extensions work. Google wants to drop all support for this version 2 from Chrome, and only allow extensions to use version 3 of the API. Chrome extensions can do their thing using a browser API called Manifest V2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |