this post was submitted on 14 Jun 2023
47 points (100.0% liked)
Technology
37712 readers
145 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
view the rest of the comments
That's one of the problems with Firefox adoption at the moment. No normie will use a browser that might not work on a given site, but no developer will test for the 1% of users
I don't know how many normal sites even have a problem with Firefox. I guess only some small, niche web apps, but otherwise most people would see no difference. Even if developers don't explicitly test on Firefox, almost all features will still just work (at least for normie usage). Power users might encounter some challenges, as the post describes.
I use Firefox btw. (not Arch though)
nameisp.com, snapchat.com, and teams.microsoft.com are the ones I can think of off the top of my head. nameisp.com is especially frustrating, because it doesn't have a "doesn't work with Firefox" banner, it just inexplicably breaks on Firefox.
Also, Firefox and Chrome handle broken XML differently, which has broken a number of internal websites for me.
Wow, you're right. Teams is not fully supported. Apparently Video and Sharing in Meetings is limited. Didn't know that. Well that sucks