I don’t know why you think that, it certainly sounds wrong to me. Like, not just wrong in a technical sense, but like, crazy wrong.
Did you live through the IE5 and IE6 days? Does the term “quirks mode” mean anything to you? Do you remember how Mac IE was completely different from Windows IE? Internet Explorer, back in the early 2000s, was a serious support burden for anyone doing web development at the time. Around 2010, Google dropped support for IE6 (in apps like GMail + Youtube) and a ton of other sites followed suit. It made a big splash across all the news sites and all the web developers breathed a sigh of relief, because they could say “we’re dropping IE6 support because Google did.”
Meanwhile, there was a parallel world of IE-only sites. Some of them were built on future widespread web technologies like DHTML, others were built on stuff like ActiveX. ActiveX ended up in the trash bin (where it belongs) and DHTML became normalized. It was… common, and annoying, to deal with corporate sites that only worked in IE, and then build your own site and fight to get it working in IE. It was not a fun time to be a web developer.
Maybe 6 or 7 years ago, I remember that Safari was missing some of the newer features that Chrome or Firefox had, but when I investigated, it usually turned out that I was using some future/experimental feature in Chrome or Firefox, and it wasn’t a problem with the standards-compliance of Safari per se. Or sometimes I was relying on behavior that was not part of the standard at all). Nowadays, my sense is that Chrome tends to have more experimental stuff available and a better set of dev tools, but otherwise, most stuff works in Safari or Firefox with little to no modification.
Things work but all too often the page renders differently. On top of that Safari only supports the part of web standards Apple agrees with. It may look like Safari supports something and then you get into it and they support like 10% of the standard, or the full standard but only on Tuesdays. It is rather annoying.
Did you live through the IE5 and IE6 days? Does the term “quirks mode” mean anything to you? Do you remember how Mac IE was completely different from Windows IE? Internet Explorer, back in the early 2000s, was a serious support burden for anyone doing web development at the time. Around 2010, Google dropped support for IE6 (in apps like GMail + Youtube) and a ton of other sites followed suit. It made a big splash across all the news sites and all the web developers breathed a sigh of relief, because they could say “we’re dropping IE6 support because Google did.”
Meanwhile, there was a parallel world of IE-only sites. Some of them were built on future widespread web technologies like DHTML, others were built on stuff like ActiveX. ActiveX ended up in the trash bin (where it belongs) and DHTML became normalized. It was… common, and annoying, to deal with corporate sites that only worked in IE, and then build your own site and fight to get it working in IE. It was not a fun time to be a web developer.
Maybe 6 or 7 years ago, I remember that Safari was missing some of the newer features that Chrome or Firefox had, but when I investigated, it usually turned out that I was using some future/experimental feature in Chrome or Firefox, and it wasn’t a problem with the standards-compliance of Safari per se. Or sometimes I was relying on behavior that was not part of the standard at all). Nowadays, my sense is that Chrome tends to have more experimental stuff available and a better set of dev tools, but otherwise, most stuff works in Safari or Firefox with little to no modification.