←back to thread

552 points freedomben | 1 comments | | HN request time: 0s | source
Show context
lapcat ◴[] No.41810286[source]
This submission title does not appear to be accurate. Here's what was actually said:

> October 9th 2024: an update on Manifest V2 phase-out.

> Over the last few months, we have continued with the Manifest V2 phase-out. Currently the chrome://extensions page displays a warning banner for all users of Manifest V2 extensions. Additionally, we have started disabling Manifest V2 extensions on pre-stable channels.

> We will now begin disabling installed extensions still using Manifest V2 in Chrome stable. This change will be slowly rolled out over the following weeks. Users will be directed to the Chrome Web Store, where they will be recommended Manifest V3 alternatives for their disabled extension. For a short time, users will still be able to turn their Manifest V2 extensions back on. Enterprises using the ExtensionManifestV2Availability policy will be exempt from any browser changes until June 2025. See our May 2024 blog for more context.

replies(3): >>41810369 #>>41810388 #>>41812034 #
wtallis ◴[] No.41810369[source]
They said "we have started disabling Manifest V2 extensions on pre-stable channels", and the "Chrome canary" referenced in the submission title is a pre-stable channel. The submission title is accurate, but narrowly highlighting only one facet of Google's update statement.
replies(1): >>41810434 #
lapcat ◴[] No.41810434[source]
That's old news, as noted in my other comment: https://news.ycombinator.com/item?id=41810420

The change here is actually about the stable channel.

Also, the title makes it sound like MV2 code has been removed from the source, but that's not the case.

replies(2): >>41810552 #>>41810624 #
1. EasyMark ◴[] No.41810624[source]
But still it’s the first stab wound inflicted on CaesarMainline, he’s toast