this post was submitted on 08 Jul 2025
633 points (98.2% liked)

Technology

72524 readers
3621 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. 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.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
633
Firefox is fine. The people running it are not (www.theregister.com)
submitted 1 day ago by eli001@lemmy.world to c/technology@lemmy.world
135 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] underline960@sh.itjust.works 14 points 5 hours ago (2 children)

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.

[–] MinusPi@pawb.social 16 points 5 hours ago (3 children)

It's so damn stupid. If your site works meaningfully differently in Firefox vs Chromium, you're already doing something very, very wrong.

[–] sheogorath@lemmy.world 8 points 4 hours ago

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.

[–] buddascrayon@lemmy.world 2 points 2 hours ago

Chromium does a lot of heavy lifting to fix problems with websites which enables certain web developers to be lazy.

[–] okmko@lemmy.world 1 points 4 hours ago* (last edited 4 hours ago) (1 children)

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.

[–] M0oP0o@mander.xyz 3 points 4 hours ago (1 children)

The how is testing on one other browser.

[–] okmko@lemmy.world 1 points 4 hours ago

What a novel idea.

[–] okmko@lemmy.world 4 points 5 hours ago* (last edited 4 hours ago)

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.