3 ms·
I don't see how that would be a true statement in almost any context, barring specifically using features that you know Chrome doesn't work well with or going t
by judge2020 7y ago
I don't see how that would be a true statement in almost any context, barring specifically using features that you know Chrome doesn't work well with or going through the chromium bug tracker to find things to do that break Chrome.
- Retric 7y agoIf developers use Firefox instead of Chrome you do get some rendering bugs in Chrome. Standard compliance have gotten much better, but at one point in my last project Edge, Safari, Chrome, and Firefox where all doing different things while I was trying to fix an odd CSS issue.
- derekp7 7y agoI had something similar, then I dug into it and found that my CSS was not specified correctly. After looking into the spec, I realized that what I thought Firefox was doing wrong, was actually the correct behavior. Chrome and Edge just covered up my mistake is all.
- greglindahl 7y agoYes. It's easy to end up being confused by different applications of Postel's Law.
- fiddlerwoaroof 7y agoThis is part of the reason I use Safari as my default browser
- ArchReaper 7y agoWhy? Safari is the worst out of all of the current options as far as CSS rendering goes.
- fiddlerwoaroof 7y agoSo not everyone on my team is using Chrome to view the sites we’re working on. But also, ime, Safari has the best UX of all the browsers I’ve tried.
- viridian 7y agoI hope this is a joke. Safari is easily the worst of the big four, and view web standards as suggestions that are to be ignored at any time. My company doesn't support IE anymore, but safari, not edge, is the new hated browser for web dev for sure.
- fiddlerwoaroof 7y agoI use Safari so that someone captures user issues that result from developing for Chrome. Other people on the team use mostly Firefox/Chrome so we have coverage of all the major browsers we target.
- robertoandred 7y agoCompared to what, Chrome? It took them how long to get position sticky, backdrop filters, etc? Meanwhile Google views web standards as their property they can willy-nilly do with what they please.
- fiddlerwoaroof 7y agoI’m still irritated that only Safari implements tail call elimination as specified in the ES6 spec.
- SalimoS 7y agoTalking from the user perspective ? The chrome/ram meme are enough to explain the issue And I’m sure macbook owners care about battery more than what you think ! And for the argument of Safari is the hated browser I’m more than okey with that at least they still test for it (I feel sorry for Firefox because the oups we didn’t test blablabla