Posts: 14,359
Threads: 9,483
Thanks Received: 9,009 in 7,160 posts
Thanks Given: 9,771
Joined: 12 September 18
31 May 24, 06:21
Quote:Google published an update on the deprecation timeline of so-called Manifest V2 extensions in the Chrome web browser. Starting this June, Chrome will inform users with classic extensions about the deprecation.
Manifests are rulesets for extensions. They define the capabilities of extensions. When Google published the initial Manifest V3 draft, it was criticized heavily for it.
This initial draft had significant impact on content blockers, privacy extensions, and many other extension types. Many called it the end of adblockers in Chrome because of that. In the years that followed, Google postponed the introduction and updated the draft several times to address some of these concerns.
Despite all the changes, Manifest V3 is still limiting certain capabilities. The developer of uBlock Origin listed some of these on GitHub. According to the information, current uBlock Origin capabilities such as dynamic filtering, certain per-site switches, or regex-based filters are not supported by Manifest V3.
The release of uBlock Origin Minus highlights this. It is a Manifest V3 extension, but limited in comparison to the Manifest V2-based uBlock Origin.
Google's Manifest V2 deprecation timeline
![[Image: chrome-extensions-support.png]](https://www.ghacks.net/wp-content/uploads/2024/05/chrome-extensions-support.png)
Google plans to show a banner to Chrome users who run Manifest V2 extensions in their browser. This starts on June 3 for development editions -- Beta, Dev, and Canary -- of the browser.
Manifest V2 extensions that have the Feature badge will lose that badge on that day.
The extensions management page in Chrome lists the soon-unsupported extensions. It provides a link to read up on the change and "find alternative" buttons next to each extension.
...
Continue Reading