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.
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.
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.
Yeah, I’m not a dev, but I work with dev teams. They all don’t test with firefox anymore. Not enough ROI according to the product managers.
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.
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.