You must log in or register to comment.
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.
Chrome is awful in nearly every way one can measure a browser. Anyone still using this as they’re main driver in 2025 is technologically challenged.
It’s wild to see Chrome going from the browser to use if you had any tech sense whatsoever to being universally derided.
Universally derided
lol try looking outside lemmy. 90% of people still just use it and don’t care
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’m gonna be honest, if they used a feature that wasn’t ready for prime time, it’s still on them.
Totally agree. It’s not the fault of Firefox at all. This is just being trigger-happy on new standards before they are ready and unwillingness to fix a problem in a different way.
It got added because it worked extremely well on browsers that implemented it, and it solved a problem that was needed on the site in question, which was very difficult to solve otherwise. I can’t blame a site for using an open standard that works for a majority of its users and which makes the development effort significantly less.
You don’t change standards to fix bad code
If only one browser runs it, it’s not a standard
This was due to Firefox at the time not implementing web standards that Chrome did.
Uhm, yeah, that’s what browsers do. There are somewhere about 150 web standards and some are hard requirement while others are soft. Blink has some implemented that Webkit hasn’t but Gecko has and that’s true for all three. Same for browsers.
Btw, the one with the most implemented standards is QtWebkit by far. It’s still slower tho.
Yeah? I’m not saying there’s anything wrong with that. I’m saying it’s bullshit to say a developer has done a crap job when one browser doesn’t implement a web standard that is perfect tailor-made for their site’s use case.
If your job is to make websites and you make sites that don’t work on a browser that has over 100 million users you’re not doing your job.
Still a bad job tho, if his implementation requires things that aren’t common and has no workarounds in place.
I like this template so much better than the Spider-Man one that people constantly use backwards.
When developing photon I always end up with more issues on chrome browsers than firefox. and half of those are because of its god awful scrollbar. Please use an overlay scrollbar instead of shifting the stupid page around, chrome.
ugh yeah classic chrome am I right? (I forgot how to center a div)
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.
How did we get from “SGML varient for formatting text” to this?
In most cases yes.
However I did find this really weird bug where Firefox was caching something to do with sockets (that would disallow connecting a new socket) that could only be cleared by restarting Firefox itself.
Is that http2? Cause http2 allows for reuse of a connection for additional requests.
This caught me out with envoy reverse proxy doing a few subdomains using a wildcard cert.
The browser would reuse the connection cause the cert authority and IP was the same, but envoy couldn’t figure out how to route the request correctly. Absolute head scratcher!
