1144
submitted 2 years ago by gaul@lemmy.ml to c/firefox@lemmy.ml
(page 2) 50 comments
sorted by: hot top controversial new old
[-] WhoRoger@lemmy.world 9 points 2 years ago

Well that's nice. But how many developers will care to make Android extensions at this point? Also will the current unsupported extensions in custom collections stop working?

[-] DuncanTDP@sh.itjust.works 9 points 2 years ago

This is seriously cool. I've been waiting for this for a while.

[-] 52fighters@kbin.social 8 points 2 years ago

Does this mean that I'll be able to get temporary containers on Firefox Android?

[-] Knusper@feddit.de 4 points 2 years ago

That extension requires rather deep integration into the UI, which I don't think is possible for Android extensions. So, I doubt, it will become available...

load more comments (2 replies)
[-] Heavybell@lemmy.world 7 points 2 years ago
load more comments (1 replies)
[-] starman@programming.dev 6 points 2 years ago

It was already possible to use all extensions on Firefox for Android Nightly

load more comments (4 replies)
[-] DefinitelyNotBirds@lemmy.world 6 points 2 years ago

Great i have been using all my fav extensions for a while in the beta version. Great news nonetheless!

[-] NickNak@lemmy.world 4 points 2 years ago* (last edited 2 years ago)

Finally! Been using ancient version due to the addon crap they pulled in the past

[-] CoyoteHart@lemmy.world 3 points 2 years ago

Kiwi Browser has been able to use a good majority of the Chrome extension repertoire already though

[-] cupcakezealot@lemmy.blahaj.zone 3 points 2 years ago

Please please please don't' bring MV3 to Firefox for Android, Mozilla. 🤞

[-] mojo@lemm.ee 7 points 2 years ago* (last edited 2 years ago)

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.

load more comments (1 replies)
[-] Private_Plan@lemmy.ml 4 points 2 years ago

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

load more comments (1 replies)
load more comments
view more: ‹ prev next ›
this post was submitted on 11 Aug 2023
1144 points (99.3% liked)

Firefox

18603 readers
20 users here now

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

founded 5 years ago
MODERATORS