this post was submitted on 11 Aug 2023
1010 points (98.9% liked)

Firefox

18053 readers
264 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] cupcakezealot@lemmy.blahaj.zone 3 points 1 year ago (3 children)

Please please please don't' bring MV3 to Firefox for Android, Mozilla. ๐Ÿคž

[โ€“] that_leaflet@lemmy.world 7 points 1 year ago

Why not? Mozilla already fixed the biggest issue plaguing MV3 by continuing to allow MV2 ad blockers.

[โ€“] mojo@lemm.ee 7 points 1 year ago* (last edited 1 year ago) (1 children)

They are, since there are definitely benefits and makes migration easier, but they are also allowing the support needed for adblockers to be just as strong as they are now. So it keeps the benefits while also keeping adblockers strong like right now.

https://blog.mozilla.org/addons/2021/05/27/manifest-v3-update/

The issue is that Chrome is trying to replace webRequest.BlockingResponse which is essential for content blockers, which Mozilla is pointing out and keeping supported.

[โ€“] Private_Plan@lemmy.ml 3 points 1 year ago

MV3 existing isn't a problem. MV2 deprecation is.