You must log in or register to comment.
I’ve been insulted by web developers for saying this before : “If your website doesn’t work on Firefox, your website doesn’t work”
If your website only works with Chrome, it’s not a website. It’s a Chrome site.
You didn’t design for the web. You designed for Chrome.
Fuck chrome. Such a dogshit unoptimized spyware browser that now disables ad-blocking plugins
I agree that Chrome fucking sucks, but it’s disingenuous to call it unoptimized. Chrome and chromium-based browsers are as fast as or faster than Firefox. Although I agree that manifest V3 is horrible to the web as a whole and shouldn’t have been created.
It also eats up like 99% of your CPU
Have you used chrome or chromium in the past few years? Source?
I was exaggerating to make a point. But one of the main reasons why I switched to Firefox (about a year ago) was because it was eating up so much of my CPU.
The problem for me is that the built-in translator is too convenient
Pretty sure Firefox have that too
I just design for IE6
That’s not necessarily true. Circa 2016–17 I frequented a website that worked in Chrome but not Firefox. This was due to Firefox at the time not implementing web standards that Chrome did. Firefox only got around to it in 2019. So naturally, the developer of the site was telling people to use Chrome.
I don’t know the history of column span but the reason Firefox was “behind” on standards was because Google was pushing new standards through committee faster than competing browsers could keep up. Google would implement a new feature, offer it as a free standard, then get it through the committee. Because Google already had it in their browser, they were already compliant while Firefox had to scramble.
It was Google doing their variation of “embrace, extend, extinguish”
It got so bad that not even Microsoft had the resources to keep up. They said as much when they said they were adopting Chromium as their engine.
This has been a problem for a very very long time
I agree with you that failing to support multiple browsers is an old problem, but I think the cause has shifted.
Back in the last century, supporting both browsers amounted to sniffing the browser and implementing the same feature twice.
document.layersvsdocument.allfor example.Nowadays I think the problem is different: we just don’t know what’s going on. The site is transpiled from TypeScript, written on top of React or Vue which drastically switches paradigm (bonus for Tailwind), packed with building tools, and the average dev has little understanding of what actually comes out. It’s a tall stack of leaky abstractions on top of the already tall one of the web. The dev is pretty sure it works on Chrome so they say it does work there, but it was not even a deliberate choice.
For most sites it’s a testing matrix issue. Most testing teams look at browser stats and choose how to apply their limited resources based on that. So the dev probably doesn’t even see the bug that exists for an old Firefox version as there’s no testing done on it.
