this post was submitted on 08 Nov 2024
578 points (98.5% liked)
Technology
59415 readers
2879 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't understand why all these chrome derivatives and firefox don't just band together and extend manifest v3 with some vendored standardised extension that addresses the limitations.
Browsers do that for CSS and JavaScript features already. An extension could just check if the browser supports the "unlimited filters" option and use it if its available.
I have never researched it but heard that the permissions of manifest v3 are much better for privacy.
I am in favor of removing manifest v2 if the vendored extension becomes a reality.
Browsers already have too much complexity, lines of code and feature creep.
Firefox implements v3 without the restrictions.
From what I understand, the limit on the lists is not the only problem with it - my main concerns are a) lists only being able to update together with the extension itself and b) some features apparently being fundamentally disallowed, like the element picker I am dependent on.