> I'm not being hyperbolic, I'm being quite literal. I tried two or three times to support Safari. I gave up on it and I'm never going back. There's nothing sp

> I'm not being hyperbolic, I'm being quite literal. I tried two or three times to support Safari. I gave up on it and I'm never going back. There's nothing special that has to be done to "support Safari" other than writing normal CSS, HTML and JavaScript just like for any other browser. Even if you used something experimental or Chrome-only, there are polyfills for most features. This only makes sense for a public facing website (e-commerce, for example), since Safari is on over a billion devices and some of those potential customers might want to use your site. > maybe Safari is fine on the desktop because I don't own a Mac so I can't test it Other than some minor differences, the latest version of WebKit is essentially the same on iOS, macOS and iPadOS. It's pretty common to use something like CodePen [1] to demonstrate CSS and HTML features publicly. [1]: https://codepen.io/ https://codepen.io/