๐ฐThe VergeโขRecentcollected in 25m
Chrome 151 ends support for legacy ad blockers
๐กChrome's shift to Manifest V3 impacts all browser-based extensions. Ensure your AI tools remain compatible.
โก 30-Second TL;DR
What Changed
Chrome 151 removes all remaining Manifest V2 compatibility code.
Why It Matters
Developers building browser-based AI tools or extensions must ensure compatibility with Manifest V3 to maintain functionality.
What To Do Next
Update your browser-based AI extensions to Manifest V3 to ensure they remain functional in Chrome 151+.
Who should care:Developers & AI Engineers
๐ง Deep Insight
Web-grounded analysis with 16 cited sources.
๐ Enhanced Key Takeaways
- โขManifest V3 replaces the
webRequestAPI with thedeclarativeNetRequestAPI, fundamentally shifting ad blocking from dynamic, real-time filtering to a static, rule-based system. - โขGoogle officially attributes the transition to Manifest V3 to improved security, performance, and user privacy, aiming to mitigate risks from malicious extensions intercepting sensitive data or injecting code.
- โขThe change significantly limits the capabilities of ad blockers, particularly dynamic filtering, custom scripting, and real-time adjustments, making them less effective against sophisticated anti-adblock techniques and comprehensive cosmetic cleanup.
- โขuBlock Origin Lite, the Manifest V3-compliant version, is a simplified alternative that lacks the full customization and power of the original uBlock Origin, which relied on Manifest V2's dynamic capabilities.
- โขThe removal of the
kExtensionManifestV2Disabledflag in Chrome 150 and other legacy flags in Chrome 151 eliminates previous technical workarounds, definitively ending any remaining support for Manifest V2 extensions.
๐ Competitor Analysisโธ Show
| Browser/Extension | Manifest V3 Compatibility | Ad Blocking Capability (Post-MV3) |
|---|---|---|
| Google Chrome | Fully Manifest V3 compliant | Limited; relies on declarativeNetRequest API, reducing dynamic filtering and cosmetic blocking effectiveness. |
| Firefox | Supports Manifest V2 and full webRequest API | Full capability; uBlock Origin functions without Manifest V3 restrictions. |
| Brave Browser | Chromium-based, but bypasses extension limitations | Built-in ad-blocking engine, not reliant on extension framework. |
| Microsoft Edge | Chromium-based; likely to follow Chrome's MV3 enforcement | Expected to be limited similar to Chrome. |
| Opera | Chromium-based; likely to follow Chrome's MV3 enforcement | Expected to be limited similar to Chrome. |
| AdGuard (Extension) | Fully adapted to Manifest V3 | Rewritten to work within MV3 constraints, combining declarativeNetRequest rules and cosmetic filtering for strong performance. |
| uBlock Origin Lite | Fully Manifest V3 compliant | Simplified, less effective at blocking trackers and dynamic elements compared to original uBlock Origin. |
๐ ๏ธ Technical Deep Dive
- API Shift: Manifest V2 utilized the
webRequestAPI, allowing extensions to actively intercept, inspect, and modify network requests in real-time. Manifest V3 replaces this with thedeclarativeNetRequest(DNR) API, where extensions provide a static list of rules for the browser to execute, limiting dynamic request modification. - Background Processes: Manifest V3 replaces persistent background pages with ephemeral service workers. These service workers are activated only when needed and shut down after periods of inactivity, impacting extensions requiring continuous background operation.
- Code Hosting: Manifest V3 bans remote-hosted code, requiring all extension logic to be included in the extension package at submission time, which enhances security but restricts dynamic updates or content.
- Permissions Model: Manifest V3 tightens host permissions, enabling users to grant permissions to specific sites rather than providing blanket access across all sites.
- Rule Limitations: The
declarativeNetRequestAPI imposes limits on the number of static filtering rules an extension can apply, potentially affecting the comprehensiveness of ad blockers.
๐ฎ Future ImplicationsAI analysis grounded in cited sources
Ad blocker effectiveness will diminish on Chrome.
Manifest V3's restrictions on dynamic filtering and real-time adjustments will make it harder for ad blockers to combat evolving anti-adblock techniques and perform comprehensive cosmetic filtering.
Users prioritizing ad blocking may migrate to alternative browsers.
Browsers like Firefox and Brave, which maintain more powerful ad-blocking capabilities outside of Chrome's Manifest V3 limitations, are likely to attract users seeking robust content blocking.
Innovation in ad-blocking solutions will shift.
Developers may explore alternative methods such as DNS-level blocking, browser-integrated solutions, or more sophisticated Manifest V3-compliant approaches to circumvent the new restrictions.
โณ Timeline
2019
Google first announced the Manifest V3 migration.
2021-01
Manifest V3 was released in stable Chrome.
2022-01
Manifest V3 became mandatory for new Chrome Web Store submissions.
2023-11
Google released a new timeline for Manifest V3 transition.
2024-06
Manifest V2 phase-out began in pre-stable Chrome (Dev, Canary, and Beta) with Chrome 127.
2024-10-10
Manifest V2 disabling reached stable Chrome (Chrome 127+).
๐ Sources (16)
Factual claims are grounded in the sources below. Forward-looking analysis is AI-generated interpretation.
๐ฐ
Weekly AI Recap
Read this week's curated digest of top AI events โ
๐Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: The Verge โ