While Postponing Manifest V3, Google Grants Adblockers In Chrome A Another Year.

by | Mar 7, 2024

Google stated last year that it will gradually replace Manifest V2-based browser extensions with new Manifest V3 standards. Developers contend that despite the “peace of mind” and greater safety that Manifest V3 claims to provide, the new regulations hurt innovations, degrade performance, and render content blockers unusable. Google had originally planned to remove Manifest V2 extensions from Chrome in January 2023, but it has now changed its mind.

You could also refer our other articles regarding Google’s ManifestV3 implementation by clicking here.

An updated timeline for transitioning from Manifest V2 to Manifest V3 is provided by the firm in a new blog post on the Chrome Developers website. Google is still on pace to stop supporting outdated extensions, but developers and users have an extra year to use and support Manifest V2-based extensions. The updated plan states that Google will take them out of the Chrome Web Store in January 2024.

Along with the revised deadline, Google has stated that it intends to deprecate Manifest V2 gradually and experimentally in order to “ensure a seamless end-user experience.” There are two phases to this strategy:New flags will be added to Chrome 112 in January 2023 to disable Manifest V2 in Canary, Dev, and Beta.
The same flags will be applied to Chrome 115 in the Stable Channel in June 2023.

End-users will be able to evaluate how deleting Manifest V2 impacts their surfing experience thanks to the new experimental flags. Google encourages the publication of Manifest V3 extensions by developers during the transitional period. The updated version does not specifically state when Manifest V2 extensions would no longer function in Chrome, in contrast to the original blog post. Old extensions “may stop operating at any moment following the aforementioned dates,” the business simply states.

Google says Manifest V3 will be required for anyone wishing to receive the recently launched “Featured” label in the Chrome Web Store, giving developers an extra push in that direction. In order to make it easier for users to identify extensions that adhere to “the finest technical standards and satisfy a high quality of user experience and design,” Google utilises that badge.

Here is the revised schedule to govern the Manifest V3 implementation:

The revised schedule for managing the implementation of Manifest V3 is as follows:If a developer wishes to have their extension included with a badge in the Chrome Web Store, they must have Manifest V3 by January 2023.
Google will halt approving public Manifest V2 extensions in the Chrome Web Store in June 2023. Current Manifest V2 extensions will change from being public to being unlisted. Only direct links allow access to delisted extensions in the Chrome Web Store.
Google will eliminate all Manifest V2 extensions from the Chrome Web Store in January 2024.

Last but not least, Google affirms that Manifest V3 will be enhanced and updated in response to developer and community feedback. The corporation claims that more adjustments to the rules will be made in the future. Progress may be monitored by developers in the official documentation.

Popular content-blocking extension creators are already putting in a lot of effort to make sure they can continue to offer the same user experience after they migrate to Manifest V3. For instance, AdGuard has released its first experimental Manifest V3-based extension. The new extension shows that content blockers will survive the move to Manifest V3, even if it is far more constrained than the existing version (partially, at least). Other browser creators, on the other hand, adopt a more assertive stance and guarantee not to include such requirements in their programmes.

Statement From Google:

We thank all of our developers who have provided valuable feedback over the past year as they’ve migrated their extensions to Manifest V3. We’re excited to see the growth of adoption from developers who are creating new extensions and migrating existing ones. We also want to thank the many developers in our community who have stepped up to provide guidance to others with similar questions. If you have feedback or comments, please continue to let us know by posting to the chromium-extensions Google Group.