Firefox

17857 readers

1 users here now

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

founded 5 years ago

MODERATORS

k_o_t@lemmy.ml

1078

Prepare your Firefox desktop extension for the upcoming Android release (blog.mozilla.org)

submitted 2 years ago by gaul@lemmy.ml to c/firefox@lemmy.ml

156 comments fedilink hide all child comments

(page 2) 50 comments

sorted by: hot top controversial new old

[–] Heavybell@lemmy.world 7 points 2 years ago (1 children)

Ooo, exciting news!

load more comments (1 replies)

[–] starman@programming.dev 6 points 2 years ago (4 children)

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

load more comments (3 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

[–] shotgun_crab@lemmy.world 2 points 2 years ago* (last edited 2 years ago)

So we're finally getting official support for most extensions on android?

[–] cupcakezealot@lemmy.blahaj.zone 2 points 2 years ago (3 children)

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

[–] that_leaflet@lemmy.world 8 points 2 years ago

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

[–] mojo@lemm.ee 7 points 2 years ago* (last edited 2 years 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.

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