this post was submitted on 08 Jul 2025
839 points (98.4% liked)
Technology
72745 readers
1526 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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..."
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 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.
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.
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.
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.