In January, the company will no longer turn off the chrome browser's old extensions standard, according to the developer advocate for chrome extensions. In order to improve the security and performance of its browser, the company is currently in the process of transitioning from the Manifest V2 extension standard to the Manifest V3 standard. Critics claim that it will be harder for ad- blocking extensions to work.
Corin wrote an explainer on the controversy. The Declarative Net Request is used by ad-blocking extensions and the Web Request is used byMV3 Critics argue that the latter restricts actions legitimate extensions might take to protect user privacy. Corin's piece is well worth a read.
In late September, it was decided that the experiment to turn offMV2 in the Canary, Dev, andBeta channels would start in January, and that the stable releases of the browser would be in June, and then stopped in January. As of December 9th, it is putting future milestones under review.
The timelines have been changed to address feedback from developers. The service worker's inability to use DOM capabilities and the current hard limit on extension service worker lifetimes are some of the challenges posed by the migration. We are trying to find a solution to the latter and are using the Offscreen DocumentsAPI.
Adblock Plus supports Ghostery, despite their opposition to the changes. Advertising still provides so much of the company's income that it is sensitive when it comes to ad- blocking. Edge, Brave, and Opera are likely to be affected by the changes to the Chromium project.
It seems like there is no plan to ditch the migration toMV3 entirely. An updated phase-out plan and schedule will be announced in March.
All Rights Reserved © 2024
