18
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 17 Jun 2024
18 points (60.2% liked)
Asklemmy
44130 readers
875 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
I don’t think I’ve experienced this. Do you mean some pages not working in Firefox, but working in Chrome? That’s mainly because of parts of web standards that are ambiguous or undefined, and Firefox and Chrome have different behavior. Some web developers (read lazy web developers) don’t test in Firefox, so they write bad code. Both Firefox and Chrome follow the standards, so if web devs just stick to the standards, everything should work.
Not a dev, but I work with them. It's often the product manager that pushes an ignore everything but chrome so we can ship more features. I've seen devs argue and lose on such things.