←back to thread

552 points freedomben | 1 comments | | HN request time: 0.323s | source
Show context
freedomben ◴[] 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 ◴[] 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 #
zamalek ◴[] No.41812044[source]
Though it is less of an issue for those two, given that they have built-in adblocking. Still a laudable effort.
replies(3): >>41812214 #>>41812220 #>>41812590 #
creesch ◴[] No.41812220[source]
While adblocking has gotten most of the focus, it isn't the only functionality that is being limited or made more complicated. One of my favorite extensions is still not available for MV3 because of complications: https://github.com/openstyles/stylus/issues/1430
replies(1): >>41819340 #
1. zamalek ◴[] No.41819340[source]
Yes, hence "less of an issue," not "not an issue."