Google Chrome automatically disables uBlock Origin: Difference between revisions

← Older edit Newer edit →

VisualWikitext

@@ Line 21: / Line 21: @@
 ==Google's response==
 {{Placeholder box|If applicable, add the proposed solution to the issues by the company.}}
+As of early 2026, Manifest V3 (MV3) is the mandatory standard for Google Chrome extensions, having officially replaced Manifest V2 (MV2). The transition is complete, meaning older extensions designed for V2 are now largely unsupported or disabled in Chrome. [1, 2]
+Here is the current state and impact of Manifest V3 on users:
+Current State (2026)
+• Final Transition: Google has phased out V2, and the Chrome Web Store no longer accepts V2 submissions.
+• Performance & Security Changes: Extensions now use "service workers" instead of persistent background pages, resulting in better efficiency but less persistent background activity. Remote code hosting is prohibited.
+• Ad Blocker Status: Popular ad blockers like uBlock Origin are being forced to shift to "Lite" versions (uBlock Origin Lite) that adhere to MV3’s new limitations. [2, 3, 4]
+Impact on Chrome Users
+• Disabling Legacy Extensions: Users still running old V2 extensions will find them disabled.
+• Ad Blocker Functionality: While some studies suggest MV3 and MV2 extensions can be equally effective, the way they work has changed. Extensions now use the  API rather than blocking web requests directly, which may limit the complexity of filtering rules.
+• "Lite" Extensions: Users must update to new versions of ad blockers (e.g., uBlock Origin Lite), which may have reduced functionality compared to the original, more powerful versions.
+• Performance Boost: Because extension "background workers" run only when needed, users may experience improved browser speed and lower memory usage.
+• Improved Security: The restriction on remotely hosted code means malicious code is less likely to be injected into an extension on the fly. [3, 4, 5, 6, 7]
+Timeline Extension (For Enterprise)
+While the public rollout is complete, Google allowed for an exception: enterprise and certain users can continue using Manifest V2 extensions through specialized group policies until June 2025. However, this is not a permanent solution, and for the vast majority of users, the move to MV3 is now finalized. [1, 4]
+AI can make mistakes, so double-check responses
+[1] https://www.linkedin.com/pulse/manifest-v3-chrome-extensions-what-actually-changed-why-ioannis-bekas-hc0ff
+[2] https://blog.devops.dev/chrome-extension-development-the-complete-system-architecture-guide-for-2026-9ae81415f93e
+[3] https://www.youtube.com/watch?v=D9meVUnrqz4
+[4] https://www.reddit.com/r/google/comments/1ivrc1l/google_chrome_disables_ublock_origin_for_some_in/
+[5] https://developer.chrome.com/docs/extensions/develop/migrate/what-is-mv3
+[6] https://www.theregister.com/2026/02/06/chrome_mv3_no_harm_ad_blocking/
+[7] https://www.facebook.com/groups/2600net/posts/4099134923642935/
 ==Consumer response==
 There are doubts that MV3 does much for the security, since according to the [https://www.eff.org/ Electronic Frontier Foundation], "when a malicious extension sneaks through the security review process, it is usually interested in simply observing the conversation between your browser and whatever websites you visit"<ref name=":0">{{Cite news |last=Barnett |first=Daly |date=9 December 2021 |title=Chrome Users Beware: Manifest V3 is Deceitful and Threatening |url=https://www.eff.org/deeplinks/2021/12/chrome-users-beware-manifest-v3-deceitful-and-threatening#MV3quotes |url-status=live |archive-url=https://web.archive.org/web/20250727115638/https://www.eff.org/deeplinks/2021/12/chrome-users-beware-manifest-v3-deceitful-and-threatening#MV3quotes |archive-date=27 Jul 2025 |access-date=16 Aug 2025 |work=Electronic Frontier Foundation}}</ref>. And to quote Firefox’s Add-On Operations Manager: "they can still do that with the current webRequest API that is not blocking".<ref name=":0" />