Google: Manifest V2 Chrome Extensions To Stop Working In 2023

Google has shared the phase-out timeline for Manifest V2 Chrome extensions and its plans to bring Manifest V3 to full feature parity.

Extension capabilities are restricted using a mechanism called extension manifest. Google made available the new version, Manifest V3, when Chrome 88 was announced earlier this year.

Google first revealed the future Manifest V3 changes through a provisional document in 2019, which announced the removal of webRequest API blocking options and requirements for content blockers to switch to declarativeNetRequest.

“Years in the making, Manifest V3 is more secure, performant, and privacy-preserving than its predecessor,” said David Li, Product Manager for Chrome Extensions & Chrome Web Store.

“It is an evolution of the extension platform that takes into consideration both the changing web landscape and the future of browser extensions.”

Also Read: IT Governance Framework PDF Best Practices And Guidelines

As outlined today by Li, Google will focus the Manifest V2 extensions phase out around two specific dates:

• January 17, 2022: New Manifest V2 extensions will no longer be accepted by the Chrome Web Store. Developers may still push updates to existing Manifest V2 extensions, but no new Manifest V2 items may be submitted.
• January 2023: The Chrome browser will no longer run Manifest V2 extensions. Developers may no longer push updates to existing Manifest V2 extensions.

Google to keep improving Manifest V3 based on feedback

Until Manifest V2 Chrome extensions are fully deprecated, Google promised to continue bringing the new manifest to full feature parity with the older version and addressing the requests made by developers.

Google says it already added additional mechanisms to the new Scripting API and expanded the Declarative Net Request API to support multiple static rulesets, session-scoped rules, and filtering based on tab ID.

“In the coming months, we’ll also be launching support for dynamically configurable content scripts and an in-memory storage option, among other new capabilities,” Li added.

“These changes were crafted with community feedback in mind, and we will continue to build more powerful extension API functionality as developers share more information about their migration challenges and business needs.”

The company also plans to share additional information on how these incoming changes will affect users and extension developers.

Also Read: Steps On How To Create Complain About Telemarketing Calls

Detailed and up-to-date info on exact dates and milestone details for the Manifest V2 phase-out is available here.

A fully detailed timeline with all expected Chrome Web Store and Chrome browser behavior changes is embedded below.

Date	Chrome Web Store behavior changes	Chrome Browser behavior changes
01/17/22	• Chrome Web Store stops accepting new Manifest V2 extensions with visibility set to “Public” or “Unlisted” • Existing Manifest V2 extensions can no longer be changed from “Private” to “Public” or “Unlisted”	no change
06/01/22	• Chrome Web Store stops accepting new Manifest V2 extensions with visibility set to “Private”	no change
01/01/23	• Chrome Web Store stops accepting updates to existing Manifest V2 extensions	• Chrome stops running Manifest V2 extensions • Enterprise policy can let Manifest V2 extensions run on Chrome deployments within the organization.
06/01/23	no change	• Manifest V2 extensions no longer function in Chrome even with the use of enterprise policy

Controversy behind the transition to Manifest V3

In the initial Manifest V3 version, Google changed webRequest’s API so that extensions could only monitor browser connections but not alter any of the content before being displayed.

The new declarativeNetRequest API was also changed to tell the browser, not extensions, to strip content or resources from visited sites. The biggest drawback to these changes was that this API came with a limit of 30,000 rules, drastically limiting ad blockers’ functionality.

As uBlock Origin’s Raymond Hill said at the time, ad blockers that rely on webRequest API’s original functionality need more rules than are available in the declarativeNetRequest API.

As Google told BleepingComputer at the time and confirmed by Li today, “these changes are in the design process,” with the company still adding new features and capabilities based on developer and user feedback.

Li also said today that Google continues to work with other browser vendors in the Web Extensions Community Group to build a common cross-browser extension model.