this post was submitted on 17 Jun 2024
18 points (60.2% liked)
Asklemmy
43796 readers
786 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Don't you think that it may be because Firefox is pretty much the only browser using a different engine that Chromium? There are literally two major browser engines, and you're developing for one them. Ofc everything else will act like Chromium, because they are Chromium for the most part.
That's all really nice. But the fact is, we use what works. It's a pragmatic decision. They're are so few Firefox users and on the end issues are not very common.
The number of Edge users is only a few % more, do you skip that too? Just check Chrome and Safari and call it a day?
As someone that uses only Firefox and knows others who do, this really surprises me. If a website is broken on Firefox then it's shitty webdev work and I'll find another store.
Edge is the same as Chrome, so no extra testing is needed for that.
Yes, Edge has transitioned to using their own forked version of Chromium under the hood, but they make enough changes that it's necessary to test for. It's not like Cromite that takes Chromium and removes some things and change configs. They modify core components of the engine itself.
Everything works fine in edge. Only Firefox has issues.
Users don't care why that is. If their app doesn't work they won't use this niche browser that very few people use.
Funny, we get more complaints about DuckDuckGo browser than anything else, and that's one of the few we don't test on. I know this because I make it a point to have someone from CS tell me about consistent pain points users are having. I wonder how many complaints about Firefox not working your customer service team is getting daily and you just don't hear about it because they've been told to tell users "just say Firefox isn't a supported browser and to try installing Chrome."
You should ask someone in CS. Whichever agent bullshits the least (not the manager) - you might learn something.
Almost 3/10 people accessing your sites are using Firefox. All those "images not loading right or whatever" are probably blatant to them, making them think "wow, what an absolute shit website."
3 out of 10.
Im grateful for you suggestions and your calls for me to learn something. I'm sure they are well meaning and not as patronising as they sound at first.
The facts are : we don't get many Firefox users. As far as we know most things are functional if not 100% visually correct. We don't tell anyone not to use Firefox. I personally have stopped using Firefox because of broken apps (not mine specifically).
I don't need to defend my position here. I don't care why apps are not working, they just aren't and I need them. Anyone can scream and cry how this is not firefoxes fault - nobody cares while the apps still aren't running.