this post was submitted on 01 Jun 2024
7 points (100.0% liked)

Technology

37750 readers
219 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Kissaki@beehaw.org 3 points 5 months ago* (last edited 5 months ago) (1 children)

Firefox plans to support Manifest V3 because Chrome is the world's most popular browser, and it wants extensions to be cross-browser compatible, but it has no plans to turn off support for Manifest V2.

If Google decided to break V2 compatibility with V3, Mozilla should announce V4 (or V3 extended), which is V3 but with the missing stuff readded.

That'd be a good practical and great product/tech marketing move. Just like most people won't see how V3 is worse than V2, V4 will indicate it's the evolved and improved V3.

It would also simplify supporting V3 and V4 at the same time for extension authors. A great practical gain for extension authors, not having to read and understand two manifest schemes and APIs.

[–] acockworkorange@mander.xyz 1 points 5 months ago

Mozilla’s V3 implementation already extends out removing artificial limitations from it. Mozilla’s doing a reverse E3 and I’m all here for it.

Now if only the nincompoop IT dept on my company allowed me to run Firefox…