
AI Summary
Google is phasing out Manifest V2 for Chrome, leaving many legacy extensions non-functional. Developers are raising concerns about the loss of core features as the V3 mandate takes hold.
- •Google has initiated the removal of Manifest V2 support for Chrome extensions, forcing developers to migrate to the V3 framework.
- •Developers report that V3 is designed to prioritize browser security and performance by limiting how background tasks and network requests are handled.
- •Data from developer discussions on Hacker News indicate that many legacy ad-blockers and privacy extensions remain incompatible or have lost core functionality during the transition.
- •The full scope of how many active extensions will cease to function by the final cutoff remains uncertain as Google continues the staged rollout.
Google has officially begun the transition process, moving Chrome extensions away from the Manifest V2 framework to the newer Manifest V3. This change follows years of planning to limit the power of background processes and improve general browser security. However, developers discussing the shift on Hacker News note that the mandatory move breaks several privacy-focused tools that rely on V2's specific permission models. Whether current extension functionality can be fully replicated in V3 remains a point of contention for many active developers.
Sources
Get the story before everyone else.
1-minute briefings. Zero noise. Straight to your inbox.
Join 1,200+ readers
Discussion
No comments yet. Be the first to start the conversation!