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.
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.
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.
This is like telling people that they are doing something wrong when they don’t “buy low and sell high” when they’re trading. Obviously. Issues with browser parity are born from a difficulty of the how and the when, not the what.
It’s ironic that I use Firefox personally but unfortunately we prioritized Chrome when I did more front end work too. Firefox would often render views differently compared to Chrome (Safari was also a shetshow) and we had to prioritize work ofc, especially for legacy stuff.
The thing is, as a pure guess, I would bet that it’s Chrome that’s not adhering to the web standards.
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.
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.
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.
Chromium does a lot of heavy lifting to fix problems with websites which enables certain web developers to be lazy.
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.
This is like telling people that they are doing something wrong when they don’t “buy low and sell high” when they’re trading. Obviously. Issues with browser parity are born from a difficulty of the how and the when, not the what.
The how is testing on one other browser.
What a novel idea.
It’s ironic that I use Firefox personally but unfortunately we prioritized Chrome when I did more front end work too. Firefox would often render views differently compared to Chrome (Safari was also a shetshow) and we had to prioritize work ofc, especially for legacy stuff.
The thing is, as a pure guess, I would bet that it’s Chrome that’s not adhering to the web standards.