I held off on Windows 10 for as long as I could until Adobe, and therefore my job, required it. Now this nonsense. I hope this isn’t the start of them joining on the web DRM bandwagon.
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.
If safari is supported, then there is no reason to not supporting Firefox. What key features supported by safari required by adobe that’s not supported by Firefox?
Out of all the modern browsers, it’s always Safari that I end up needing to write compatibility code for. I’m sure the app works fine on Firefox, they just haven’t tested it.
Which is really sad because Safari used to be one of the best browsers over a decade ago now.
Tbf, while daily-driving Firefox I do occasionally encounter websites (mostly web apps) that do not work on Firefox. But it’s often a pretty simple fix, like sometimes I can get around it myself just through Dev Tools shenanigans.
QA is probably just not testing on FF because of user share. And if it’s not going through QA, you just don’t support it as bog coorp…