![]() "When it migrates to MV3, we're confident it will be almost as good in terms of content blocking. "Take our MV2 ad blocking extension for example," he commented. His overall assessment of Manifest V3 is that "things are far from terrible." He credits Google for actually engaging with the web community through the formation of the W3C WebExtensions Community Group. Meshkov pointed to a piece he wrote on the topic on November 3. However, there are still shortcomings and limitations." "What's true about that is that I am indeed much more optimistic about MV3 than I was two years ago. "I guess it's natural that Google chose to use an optimistic quote in their public communication," he told The Register. The Register asked Meshkov whether that passage accurately reflects his assessment of Manifest V3, and his answer was more circumspect. As always, migrating to a new platform is a large undertaking, but we're very hopeful that the new unified platform will bring substantial benefits to the entire browser extensions ecosystem, and that ad blockers like us will be able to continue being up to the task and further improve. With Manifest V3, we've observed the immense effort that browser teams (Chrome in particular, but also other browsers) are putting into working on a unified platform, and I see how they are listening to the feedback from extension developers. Li's post cites an endorsement from Andrey Meshkov, CTO of AdGuard, which makes content blocking tools including a browser extension. Those expectations appear to be lower than Google would have people believe. "Specifically, we are encouraged by our ongoing dialogue with the developers of content blocking extensions, who initially felt Manifest V3 could impact their ability to provide users with the features they’ve come to expect," he said. And the mega-corp's financial risk boilerplate makes clear that the ad giant wants investors to know that content blocking poses a revenue threat.Ĭiting work done on various Manifest V3 capabilities, such as support for Offscreen Documents, better management options for service workers, and a new User Scripts API, Li signaled the adoption and/or acceptance of Manifest V3 has increased significantly. Google's Chrome team has insisted it isn't out to kill content-blocking extensions, but its conciliatory messaging has been muddied by YouTube's deployment of scripts to detect ad-filtering extensions and warn people that such tools are against its terms of service. ![]() At least one widely used extension, uBlock Origin, is expected not to be ported, though its author has created uBlock Origin Lite, a less capable but nonetheless functional ad blocker for Manifest V3. But the consequence of the platform rewrite is that certain capabilities will be lost or diminished, notably content blocking. Instead V3 offers an API called clarativeNetRequest that performs a similar function but asynchronously (synchronous operations block other tasks until they're done) and by most accounts less effectively.įor developers, the Manifest V3 transition means translating extension code into a new grammar that in some cases lacks words that mean the same thing, or have subtle differences.Īs unpopular as it seems, Google's rationale for creating Manifest V3 was sound – Manifest V2 extensions were quite powerful and could be easily abused. Manifest V3 no longer supports the blocking version of chrome.webRequest, ostensibly as we said above for the sake of performance and security (enterprise and education installations excepted). Developers of content-blocking extensions could use this to intercept, block, or modify data (eg, ads) requested by the browser from websites. More broadly, it refers to the set of functional options available to browser extensions.įor example, the most significant change between Manifest V2 and Manifest V3 is that the older specification supports the blocking version of the chrome.webRequest API. The name refers to the numeric value for the manifest key in the manifest.json file, which is where browser extensions declare their required permissions and capabilities. Manifest V3 is supported by other browsers – Edge, Firefox, and Safari – to wildly varying degrees. That means the end of your Manifest V2-based ad blocker a Manifest V3 version, if available, will work. ![]() "Users impacted by the rollout will see Manifest V2 extensions automatically disabled in their browser and will no longer be able to install Manifest V2 extensions from the Chrome Web Store." "We will begin disabling Manifest V2 extensions in pre-stable versions of Chrome (Dev, Canary, and Beta) as early as June 2024, in Chrome 127 and later," said David Li, product manager at Google, in a statement on Thursday.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |