> Why is it that Safari gets dragged for not supporting an endless rabbit hole of “web app” standards Because there's a contingent of loud HNers who reflexivel

> Why is it that Safari gets dragged for not supporting an endless rabbit hole of “web app” standards Because there's a contingent of loud HNers who reflexively drag Apple and Safari because they believe: A. Apple is intentionally limiting Safari to protect its App Store business B. Apple is some kind of illegal monopoly for only allowing (for now) WebKit as the browser engine on iOS and iPadOS; therefore Apple is evil. C. Safari is still the buggy and slow to adopt web standards browser from 5 years ago, even though most of them haven't used or tested against it since then. Some of these people claim Safari is the new IE; either they have amnesia or weren't doing web development when IE 6 was the bane of every developer's existence; otherwise they would know better. D. All the above… and more. > nobody cares that Chrome and Firefox haven’t found the time to get P3 color working in five or six years? Unfortunately because Chrome has approximately 70% of the browser market and Firefox's marketshare is in the single digits, if a feature doesn't ship in either browser, it's like the feature itself doesn't exist. Same thing with the :has() selector… the most anticipated CSS feature probably ever. Safari shipped it in March of 2022 and usual suspects acted like it was no big deal. Chrome didn't ship it until the end of August and Firefox still hasn't shipped. And even though progressive enhancement is a thing, many of the most vocal posters on HN don't seem to practice it. They could use the following media query to test for a P3 display, supported by Chrome and Safari: @media screen and (color-gamut: p3) {…}