The group also refused to block tracking cookies until it can first build a tracking and advertising system into Chrome (this has also been repeatedly delayed). The Chrome team seems committed to a heel-turn lately. If Google's worried about security, it could police the extension store better. The EFF also says performance isn't a valid excuse either, citing a study showing that ad downloading and rendering degrades browser performance. The EFF said Manifest V3 "will restrict the capabilities of web extensions-especially those that are designed to monitor, modify, and compute alongside the conversation your browser has with the websites you visit." The privacy group said it's "doubtful Mv3 will do much for security," too, since it only limits filtering website content, not collecting it, so malicious extensions could still vacuum all your data. The Electronic Frontier Foundation is not buying Google's sales pitch and called Manifest V3 " deceitful and threatening" around a year ago. The old timeline would have finally implemented the full Manifest V3 transition six years after this initial blog post, but now it sounds like it will take even longer. The fun side-effect of all that is more limited ad blocking, which would conveniently help Google's bottom line. Google started this mess in 2018 with a blog post outlining a plan for "Trustworthy Chrome Extensions, by default." As part of the Manifest V3 rollout, Google's official story is that it wanted to cut down on "overly-broad access" given to extensions and that a more limited extension platform would "enable more performant" extensions. Google's delay is only about trying to fix some of these background limitations. Google wants all background processing to happen in service workers, but that's a complicated environment compared to normal web development and comes with many more limitations. Google's statement only addresses the second controversial change to Manifest V3: turning off an extension's ability to launch a hidden background page due to background processing. We’re mitigating the former with the Offscreen Documents API (added in Chrome 109) and are actively pursuing a solution to the latter." After adding that every step of the timeline is on hold, Vincent said, "Expect to hear more about the updated phase-out plan and schedule by March of 2023." The new timeline is that there is no timeline, and every step is now listed as "postponed" or "under review."įurther Reading Google delays death of tracking cookies again, wants more time for “testing”In a post about the delay, Chrome Extensions Developer Advocate Simeon Vincent says, "We’ve heard your feedback on common challenges posed by the migration, specifically the service worker’s inability to use DOM capabilities and the current hard limit on extension service worker lifetimes. This would move to the stable version in June, with the Chrome Web Store banning Manifest V2 extensions in January 2024. The old timeline started in January 2023, when beta versions of Chrome would start running "experiments" that disable Manifest V2. The first steps toward winding down Manifest V2 were supposed to start January 2023, but as 9to5Google first spotted, Google now says it delayed the mandatory switch to Manifest V3 and won't even have a new timeline for a V2 shutdown ready until March. The new extension system, called "Manifest V3," technically hit the stable channel in January 2021, but Chrome still supports the older, more powerful system, Manifest V2. For several years now, Google has wanted to kill Chrome's current extension system in favor of a more limited one, creating more restrictions on filtering extensions that block ads and/or work to preserve the user's privacy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |