In the upcoming Chrome 150 release on June 30, support for the kExtensionManifestV2Disabled flag will be removed, which allowed the installation of add-ons using the second version of the Chrome manifest from the Chrome Web Store. Two days ago, code implementing the AllowLegacyMV2Extensions parameter, which allowed developers to manually load extensions based on the second version of the manifest, was also removed from the Chromium codebase, which serves as the basis for the Chrome 151 release scheduled for July 28. Just a few days prior, the Chromium codebase saw the removal of the kExtensionManifestV2Unsupported and ExtensionManifestV2Availability parameters, which were declared unsupported about a year ago.
Participants of the uBlock Origin project recommended that Chrome users switch to other browsers or switch to the uBlock Origin Lite extension, which is developed by the author of uBlock Origin and is a version of uBlock Origin adapted to the declarative API proposed in the third version of the Chrome manifest (declarativeNetRequest). Support for the second version of the Chrome manifest is present in Firefox and Safari and will also be retained in Brave and Opera browsers based on the Chromium engine.
The third version of the Chrome manifest, which defines the capabilities and resources available for extensions written using the WebExtensions API, is developed as part of an initiative to simplify the creation of safe and high-performance extensions. The main complaint about the third version of the manifest is the transition of the webRequest API to read-only mode, which allowed for custom handlers with full access to network requests and the ability to modify traffic on the fly. Instead of the webRequest API, the third version of the manifest introduces the limited-capability declarativeNetRequest API, which provides access to a built-in filtering engine that independently processes blocking rules and does not allow the use of custom filtering algorithms.
The uBlock Origin Lite (uBOL) extension implements only a portion of uBlock Origin's functionality. It has proven difficult to transfer dynamic content filters and URLs, HTTP header filters, tools for disabling scripts, fonts, and large multimedia elements tied to specific sites, many filter options (strict1p, strict3p, domain, redirect-rule, removeparam), and DNS manipulation protection to bypass blocks. Due to the requirement for additional permissions, cosmetic filters for replacing content on the page ("##"), script substitutions on sites ("##+js"), request redirect filters ("redirect="), CSP (Content Security Policy) header filters, and request parameter removal filters ("removeparam=") are disabled by default in uBlock Origin Lite.
Source: opennet.ru
