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.
I switched from Chrome to Firefox at work recently once they added tab groups. A few parts of one of the web apps my team maintains straight up don’t work. I mentioned it in a meeting, received a full 10 seconds of silence before someone said “Well customers aren’t complaining…”
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.
I switched from Chrome to Firefox at work recently once they added tab groups. A few parts of one of the web apps my team maintains straight up don’t work. I mentioned it in a meeting, received a full 10 seconds of silence before someone said “Well customers aren’t complaining…”
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.