Firefox

20317 readers

186 users here now

/c/firefox

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

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago

MODERATORS

k_o_t@lemmy.ml

golden_zealot@lemmy.ml

115

Mozilla’s approach to Manifest V3: What’s different and why it matters for extension users (blog.mozilla.org)

submitted 4 months ago by neme@lemm.ee to c/firefox@lemmy.ml

3 comments fedilink hide all child comments

top 3 comments

sorted by: hot top controversial new old

[–] iamdefinitelyoverthirteen@lemmy.world 13 points 4 months ago

Yup, still no ads.

[–] thingsiplay@beehaw.org 13 points 4 months ago

Google began phasing out Manifest V2 last year and plans to end support for extensions built on it by mid-2025. That change has real consequences: Chrome users are already losing access to uBlock Origin, one of the most popular ad blockers, because it relies on a Manifest V2 feature called blockingWebRequest.

I'm actually a little bit surprised that Mozilla directly calling out Google by name and what they do, in an explicit manner.

[–] plz1@lemmy.world 12 points 4 months ago

Mozilla’s approach to Manifest V3 prioritizes user choice and control, offering developers more APIs and supporting both Manifest V2 and V3. This contrasts with Google’s approach, which limits extension functionality and will phase out Manifest V2 by mid-2025.