2026-04-02 17:39 UTC
@adactio I have not read the article yet, and am replying partly to bookmark this for myself to read when I have more time later.
I do agree that Apple sometimes supporting their own standards instead of common/open standards is frustrating. (ex: requiring Apple audio containers for some codecs)
BUT, I'm also wary of "The Web" requiring supporting *every* web standard and every feature that Google's Chrome supports. Web sites *should work* on older/smaller browsers, or for example, without JS!
Replies (2)
-
@cwilcox808@c.im 2026-04-02 20:42
@NfNitLoop Yeah, this isn't about keeping up with what Chrome churns out but Safari's tendency to have regressions in well established HTML standards. I've repeatedly seen this with Safari and details / summary elements, particularly its representation in the accessibility tree. @adactio
-
@adactio@mastodon.social 2026-04-03 08:21
@NfNitLoop Read the article. You’re talking about something completely different.