The reason for this disruption is that Google is moving Chrome to the new Manifest V3 version, which directly affects the way extensions work, including uBlock Origin.
The demand for ad blockers has been on the rise lately. Users are turning to tools like uBlock Origin to cut down on ads, especially since Google platforms like Chrome and YouTube have been criticized for their tight control over how ads are displayed. However, according to a report from The Verge, uBlock Origin is currently experiencing issues on Chrome. Users who attempt to use the extension are receiving a message saying their device is “no longer supported.”
The issue stems from Google's move to the new Manifest V3 platform for all of Chrome. uBlock Origin, which worked fine on Manifest V2, is no longer functioning properly due to changes in the way Chrome handles requests from extensions. To address this, the uBlock Origin developers have released a replacement version called uBlock Origin Lite (uBOL). However, they admit that this version is less efficient than the original.
According to the developer, uBlock Origin Lite is limited by the new Manifest V3 model, which reduces its ability to handle ads and other content on websites. Since many filters cannot be converted to DNR (Declarative Network Request) rules under Manifest V3, uBOL will be less effective at blocking content and will have limitations when handling complex websites.
Google has confirmed that over 93% of extensions in the Chrome Web Store have now migrated to using Manifest V3. This includes content filtering extensions like uBlock Origin. Google also announced that support for Manifest V2-based extensions will end this year, with the full transition to V3 expected to be complete by 2025.
This change has caused quite a few difficulties for users, especially those who rely on ad blockers for a comfortable and less disruptive browsing experience.
Hung Nguyen (According to 9to5google)
Source: https://www.congluan.vn/trinh-chan-quang-cao-ublock-origin-bi-vo-hieu-hoa-tren-google-chrome-post317016.html
Comment (0)