Google Chrome’s Endgame for Manifest V2 Extensions
Google Chrome’s transition from Manifest V2 (MV2) to Manifest V3 (MV3) is nearing its final phase, marking a significant shift in the browser’s extension ecosystem. This mirrors the browser wars of the early 2010s, where Chrome’s rise to dominance led to a flurry of extension development. Now, as Chrome prepares to axe MV2 support, extension developers and users alike must adapt.
The writing on the wall came when Chromium contributor Andrey Bershanskiy shared details on the w3c WebExtensions Community Group GitHub repo. Google engineer Devlin Cronin confirmed that Chrome has started removing flags controlling MV2 availability, effectively ending support for MV2 extensions like uBlock Origin. This move is driven by growing technical difficulties, implementation complexities, and security concerns.
This decision has significant implications for the Chrome extension ecosystem. Developers will need to update their extensions to MV3 to ensure continued compatibility, while users may need to seek alternative browsers or extension options. The transition period is expected to be short-lived, with Chromium version 151 marking the end of MV2 support.
Chrome’s Decision Logic and Mechanics
Google’s decision to end MV2 support is likely driven by the need to simplify its extension ecosystem and improve security. By removing the kExtensionManifestV2Disabled feature flag, Chrome is effectively killing all uBlock Origin bypasses. This move is consistent with Google’s broader strategy to streamline its browser and improve user experience.
The operational mechanics of this change involve removing the associated functionality and code for MV2 extensions. While this may seem like a drastic move, it’s a necessary step to ensure the long-term viability of Chrome’s extension ecosystem. Developers will need to adapt to the new MV3 standard, which offers improved security and performance features.
The tradeoffs for this change are significant. Users will need to update their extensions or seek alternative browsers, while developers will need to invest time and resources into updating their extensions. However, the benefits of a streamlined and secure extension ecosystem outweigh the costs.
Winners, Losers, and Disrupted Parties
The winners in this scenario are Google and Chrome users who value a streamlined and secure extension ecosystem. The losers are extension developers who will need to invest time and resources into updating their extensions, as well as users who rely on MV2 extensions like uBlock Origin.
Adjacent markets, such as Mozilla Firefox, may also benefit from this change. Firefox is an excellent alternative for users who want to continue using MV2 extensions, and its MV3 support ensures a smooth transition for users who want to switch.
The impact of this change will be felt throughout the browser ecosystem. Users will need to adapt to new extensions and browsers, while developers will need to invest in updating their extensions. The downstream effect of this change will be a more streamlined and secure browser ecosystem.
The Skeptical Case
A skeptical view of this change might argue that Google is overstepping its bounds by ending support for MV2 extensions. This move could be seen as a power grab, forcing developers to adapt to a new standard that may not be compatible with their existing extensions.
Historically, similar moves have backfired. For example, Microsoft’s decision to end support for Internet Explorer led to a backlash from users and developers. Google’s move to end MV2 support could have similar consequences, particularly if users feel forced to switch to alternative browsers or extensions.
The Signal to Watch Next
The next verifiable event to watch is the release of Chromium version 151, which marks the end of MV2 support. This release will confirm whether Google’s decision to end MV2 support is final and irreversible.
Another signal to watch is the reaction of extension developers and users. If developers are unable to update their extensions in time, or if users are forced to switch to alternative browsers, this could lead to a backlash against Google.
What’s your take on this? Drop your perspective in the comments below.
By Alex Mercer, Senior Tech Analyst at TrendFlashy
Ready to launch your own asset?
Check out our guide on Building a Profitable Online Business.
