Sadly I am running into more and more things that don’t work on firefox. Stuff like medical record portals, financial websites for my companies retirement plan. Stuff I have little choice about. And most fail silently. They don’t say it is the browser. I don’t know how they are doing it, but google is winning the fight.
When I asked a couple of developers who work on websites/webapps with a lot of moving parts, they said it was easiest to just test for chrome, since that’s what most people use.
Smae thing that Nvidia does with OpenGL. Their driver handles a lot erroneous out of spec behaviour so developers think their game works fine but the moment you run it on AMD or Intel GPUs, you get all sorts of issues because they actually implement the spec accurately.
If a site I have to use doesn’t work for no apparent reason, I e-mail the company’s Support. Let them sort it out, or provide another way I can do what I’m trying to do. Personally, I think a lot of the problems are from more and more websites integrating privacy-invading “features”, and FF interfering with their operation.
Stuff like medical record portals, financial websites for my companies retirement plan. Stuff I have little choice about. And most fail silently.
I recall how South Korea literally painted itself into a corner for becoming too dependent on Internet Explorer after years of using it with a security implementation based entirely on ActiveX.
I’m currently using a user-agent switcher plugin. Allows me to spoof servers into believing I’m running a different browser.
I tried the spoofer on a few, and they still failed. I thought it was supposed to be all chromium under the hood, but somehow it’s different. And companies don’t test firefox, nor care.
Sadly I am running into more and more things that don’t work on firefox. Stuff like medical record portals, financial websites for my companies retirement plan. Stuff I have little choice about. And most fail silently. They don’t say it is the browser. I don’t know how they are doing it, but google is winning the fight.
When I asked a couple of developers who work on websites/webapps with a lot of moving parts, they said it was easiest to just test for chrome, since that’s what most people use.
It’s turned into a self-fulfilling prophecy.
It’s so damn stupid. If your site works meaningfully differently in Firefox vs Chromium, you’re already doing something very, very wrong.
Yep, this is why at least for me when I develop websites I use Firefox first for development to make sure that the website runs on Firefox.
Chromium does a lot of heavy lifting to fix problems with websites which enables certain web developers to be lazy.
Smae thing that Nvidia does with OpenGL. Their driver handles a lot erroneous out of spec behaviour so developers think their game works fine but the moment you run it on AMD or Intel GPUs, you get all sorts of issues because they actually implement the spec accurately.
If a site I have to use doesn’t work for no apparent reason, I e-mail the company’s Support. Let them sort it out, or provide another way I can do what I’m trying to do. Personally, I think a lot of the problems are from more and more websites integrating privacy-invading “features”, and FF interfering with their operation.
I recall how South Korea literally painted itself into a corner for becoming too dependent on Internet Explorer after years of using it with a security implementation based entirely on ActiveX.
I’m currently using a user-agent switcher plugin. Allows me to spoof servers into believing I’m running a different browser.
I tried the spoofer on a few, and they still failed. I thought it was supposed to be all chromium under the hood, but somehow it’s different. And companies don’t test firefox, nor care.