←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 #
1. sebazzz ◴[12 Oct 24 08:29 UTC] No.41817483[source]▶
That is easy talking as long as it is still a config flag, then after a compile-time flag. Once the internal APIs for MV2 or where MV2 get removed or changed it becomes very difficult to maintain. Never mind the possible security issues you introduce, but won’t get so quickly discovered.