Is there a reason why? Less funding? Web devs don’t make the pages Firefox friendly? Since the user base is smaller, they just don’t care?
Hmm, do you mean in the web console?
I know Firefox has a bit of a reputation for being rather precise in how it handles web standards compliance. So, it’ll show comparatively many warnings and errors, if you don’t keep to the web standards.
This is actually quite useful for web devs, because it means, if Firefox is happy with your implementation, then it’s relatively likely to run correctly on all browsers.
Yeah, if that’s what OP means (though that’s unclear), I’m not sure why OP thinks it’s a bad thing. It’s a good thing.
Or maybe OP means Firefox crashes more or something. In which case I can only say that hasn’t been my experience.
My experience has been, however, that Firefox is quite usable on a Raspberry Pi 4 while Chromium is far too resource hungry to be usable on that platform.
Web devs don’t make the pages Firefox friendly? Since the user base is smaller, they just don’t care?
correct
also in the case of Google controlled websites the errors are often deliberately introduced to sabotage firefox
Wait, what? Do you have a source on this?
The browser war has been long and bloody, but here’s a current battle.
https://fosspost.org/google-slowdown-firefox-users-when-watching-youtube
Didn’t that turn out to be an issue related to adblockers?
I work in web and app development company and we don’t check Firefox anymore, because it’s the only outlier and has not many users. But mainly because we wouldn’t have to do it for any other browser specifically and Firefox is not special in any way. The errors come from it being more strict, which might sound good, but it’s actually really just inconvenient. The errors go from image alignment issues to apps not working at all. We don’t fix any of that.
Aaah so you and your company were proponents of the “This Site is optimised for Internet Explorer”
Ok boomer.
Woah such a scathing retort.
Perhaps consider the accessibility angle why it’s a bad idea only catering to one browser and that your team/company should do better than that.
It was humorous. I try to take stuff lightly.
Its not a bad idea. Nobody uses Firefox. We tested and there is no reason for us to start putting in the effort.
Nobody uses Firefox
well thanks to companies like yours, its not surprising that the trend is going downwards. Pfft who needs a vendor free Web after all, eh? Everything’s Google now, yay!
Were you alive during the time when IE was only supported? We don’t want to go back to a time like that. We learn from history.
I mean it’s not a bad point, IE once had the market dominance that chrome does now. By all means continue only supporting one engine but at least be aware that you’re gambling on the browser market not shifting again as it has done in the past.
Look, its not like we wont notice a shift like that. It would be very easy to adapt if the situation warranted.
deleted by creator
If you’re developing software for one client who only uses a specific browser, I can see this being okay, but several times I have chosen not to buy things from websites that were broken in Firefox. I don’t bother to check whether they’d work in Chromium, I just buy it elsewhere.
The number of people who act like me probably isn’t large in absolute terms, but how many customers have been lost because of a broken website that you didn’t even know about because they just left without a trace?
This might not apply to you, but it’s some food for thought whenever Web developers decide to be sloppy and not check compatibility for a browser that still has significant market share.
Same. I’m not bothering with broken web sites.
I’m not in the US though, so I don’t get many of them.
The number of people who act like that is negligible. We tested for that.
We don’t see it as that we are sloppy but that Firefox is not a good browser. We came to that conclusion because no other browser acts like that.
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.
We don’t see it as that we are sloppy but that Firefox is not a good browser. We came to that conclusion because no other browser acts like that.
Your views seem to be very narrow despite being a developer.
There are many misconceptions in your short sentence.
I want you to point them out.
Ah. You pray at the altar of Google with the mantra: “It only works in Chrome or Edge. Why not upgrade your browser?”
What could possibly go wrong with giving all the power to one browser engine? If only there was a precedent to learn from…
Haha, no. We don’t pray. We make web apps to make money. Catering to a negligible users who for some reason want to use the single browser with issues, that’s up to them.
I use firefox exclusively, on both my laptop and my phone. It works perfectly on any website I throw at it. I work for a startup which makes video call apps, the web client works perfectly under Firefox, and there’s a grand total of 2 devs working on it.
All this to say that if I come across your website and it doesn’t work under Firefox, AFAIC it’s your website that has issues, not Firefox.
As for the reason, you might be fine with a single megacorp dictating the way the web works, but for many of us who remember what it was like in the IE hegemony days it’s a serious concern.
Again, I’m not a soldier for any software. I don’t care. It’s a pragmatic business decision.
I guess my point is, you should :)
I would, if there wasn’t for my personal experience of using Firefox, when I had to switch to other browsers for some websites I used.
Its because of that, that when we decided to ignore Firefox, I wasn’t against it.
It’s a question of
How much effort (man hours which ultimately translates to $$$) versus how much revenue lost (people not buying because of Firefox bugs)
In my experience this depends on your specific application. Sometimes there are weird bugs or behavior where you have to really hunt down what’s going on. Other times it’s as simple as changing a few css lines or something.
It’s almost impossible to calculate revenue lost, but as much as we tried, it was 0 or almost 0.
Again, we don’t even check anymore.
Bruh, he just explained what his company’s workflow is like. He wasn’t espousing the opinions that everybody is accusing him of, just saying how his job requires him to work.
This community can be hyper-reactionary sometimes.
Do you think that this workflow is some divine commandment? Developers like him create these. He should totally get some of the blame.
Yeah I’m sure he, alone, is responsible for his company’s practices, and isn’t just a dude trying to make a paycheck.
I never said he alone did it. I’m sure he’ll be happy to share credit for any great product his company makes. Why not take some of the blame too? (I’m not sure if he does think that way though. He hasn’t replied since. I’m just replying to other people.)
Why should he take the blame for something he likely has no influence over? That’s like blaming the Sandwich Artist because you don’t like Subway’s bread; he just makes the sandwiches, he doesn’t design the recipe.
Honestly, I’d be fine and understand that he cannot but be complicit in this due to powers beyond his reach. I’d eat my words if he says that he doesn’t like it, but has to comply. But he seems like he’s pretty happy with it. (Again, from that one comment.) I will blame the sandwich artist if he defends shitty sandwiches. Because one has to be responsible for their own work. They’re free to not give a fuck about what anyone thinks. But they are complicit.
It’s funny, I am not a web developer, but have built my own page for indexing my photo galleries.
It uses a lot of CSS, and I gave up on developing for Chrome/Webkit just because it is less precise, I make it work in Firefox because then I know it works fine in Chrome.
Way more efficient.
Well no. It doesn’t work like that. Unfortunately.
It did for me…
That’s great for you. These issues are not that common really.
It’s like making a .txt document with tables and ASCII art and then on my God other text editors use different fonts and the look breaks. Only the most popular, Windows Notepad is supported.
Web was supposed to be bulletproof, easy to archive and implement. If a webpage break because a browser is supporting 99% of super bloated web standards instead of 99.5% of Chrome, there is clearly something wrong.
My rule of thumb is, try to randomly remove some HTML tags and CSS declarations. If whole site break and is unusable because of one/two lines missing, this website is a hack exploiting browser monoculture.
Again, I’m not a soldier for any particular software. I’m a pragmatic user. I will use whatever works and will develop of whatever works.
Some apps and websites are broken on Firefox, that’s why we don’t use it and don’t optimise for it. We don’t care it’s not the fault of Firefox. It’s a pragmatic business decision that is practically inconsequential, because Firefox has so few users.
I work in web and app development company and we don’t check Firefox anymore, because it’s the only outlier and has not many users.
Fellow webdev here, You’re absolutly correct.
I mostly use Firefox, so I develop on Firefox and check other browsers for issues. That way, I can make sure the app and websites I’m working on still work on Firefox.
