←back to thread

"Begin disabling installed extensions still using Manifest V2 in Chrome stable"

(developer.chrome.com)
552 points freedomben | 1 comments | 11 Oct 24 14:20 UTC | HN request time: 0s | source
Show context
freedomben ◴[11 Oct 24 14:42 UTC] No.41809900[source]▶
Notably, Firefox is not removing v2 support (at least for now as of March 2024)

> Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future. And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed.[1]

[1]: https://blog.mozilla.org/addons/2024/03/13/manifest-v3-manif...

replies(5): >>41810093 #>>41810602 #>>41812042 #>>41816445 #>>41818422 #
EasyMark ◴[11 Oct 24 15:53 UTC] No.41810602[source]▶
To my knowledge the “big” chrome engine alternatives aren’t either. I know that Vivaldi and Brave plan on keeping around v2 as long as it is economically feasible
replies(8): >>41812032 #>>41812044 #>>41812235 #>>41812473 #>>41812812 #>>41813683 #>>41816147 #>>41817483 #
Sophira ◴[11 Oct 24 19:07 UTC] No.41812473[source]▶
Are you certain? The last I heard about it from Vivaldi[0], they were only going to keep the MV2 code around so long as it's in the upstream codebase:

> We will keep Manifest v2 for as long as it’s still available in Chromium. We expect to drop support in June 2025, but we may maintain it longer or be forced to drop support for it sooner, depending on the precise nature of the changes to the code.

Note that June 2025 is the same date Google plans to drop support completely[1].

[0] https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-futur...

[1] https://developer.chrome.com/docs/extensions/develop/migrate...

replies(2): >>41812748 #>>41812787 #
bambax ◴[11 Oct 24 19:35 UTC] No.41812787[source]▶
But... what could possibly be the point of using a chromium based browser that is not Chrome, if not for MV2 support?
replies(3): >>41813627 #>>41815409 #>>41816366 #
andmalc ◴[12 Oct 24 00:50 UTC] No.41815409[source]▶
MS Edge, Arc, and Sidekick have features Chrome doesn't such as split screen, side panels, and vertical tabs. Likewise for Firefox forks such as Zen.
replies(1): >>41816690 #
aydyn ◴[12 Oct 24 05:34 UTC] No.41816690{3}[source]▶
None of those things are anything close to killer features much less reasons to switch. Verticle tabs, seriously?
replies(5): >>41816937 #>>41816938 #>>41817314 #>>41819225 #>>41819402 #
1. jocoda ◴[12 Oct 24 06:31 UTC] No.41816938{4}[source]▶
Split screen done well would be a killer feature for me. Last time I looked Edge support was ok, but not great. But what kills Edge for me as a daily driver is the basic usability in managing bookmarks and tabs. It's stop and go for every basic operation like dragging objects while Firefox is simply a continuous flow. Firefox is invisible, Edge just gets in the way all the time.

Otherwise Edge is not bad at all. Chrome without MV2 is dead to me.