If you want to make a passable UI, let chatgpt make it.
If you want to make a good UI, make it yourself.
If you want to make a great UI, test it in iOS Safari as you make it.

Safari is the new IE!

It still baffles me that label's for attribute doesn't work on macs in 2025!

To avoid this BS just wrap input with your label tag or even better write JS listener for ids that got clicked, for stellar optimization and maintenance, hardcode the ids into the function!

I ask myself daily: does this pleasure ever ends???

@devJs for attribute not working? Never happened to me ever.

What if I want to alienate apple plebs?

@kiki ok, maybe my bad - i might said some things that i didn't thoroughly checked, i remember that i used some software for scientific research recently that was made with bootstrap. Might be bootstrap's fault.

I clicked like million times on labels, nothing happened, opened on android, works like a charm!

@devJs I consider iOS Safari to be the ultimate litmus test for hacky code. Chrome is good at absorbing hacks, while Safari is more strict and exact. For example, it shouldn't be possible to synchronize positions of two elements while they're being transitioned, if one of them is moved with translate() and the other one with margin. Chrome will sync them up for you, Safari won't, because that's lowkey a hack, and you shouldn't write hacks. If you need animations to sync, animate the same exact property. Use translate() everywhere.

If my site works in Safari, I know it works everywhere. From my 10 years of experience, every "bug" that people attributed to Safari was actually their code's fault, sans some quirks that I can name. For example, Safari's 100vh, as well as position: fixed's data is not necessarily equal to the viewport data you can get with JS during and after the on-screen keyboard is being collapsed, so your fixed elements can get stuck mid-air. But thats about it really

@kiki This is exactly right. You can‘t blame Safari for not supporting hacks and other crap that isn‘t even in the standard.

@kiki well, ok i agree. I don't trust chrome for testing the CSS at all. Firefox was better as it doesn't tolerate some crazy shit that works in chrome.

I know firefox is in its decline, but good lifetime for open source one. Also tolerates less bs than chrome.

I never liked safari because its design goes against my habits, would give it a shot. Who knows maybe I'll switch from FFox

@Lensflare It also doesn't completely support the standard either so you need hacks to make it work on safari XD

@devJs chrome is the only good browser with tts and stt support. If everyone just uses chrome, we would be in a different world.

@retoor if course it would. First, they make Chromium closed-source. Then, they replace HTTP with something proprietary. Then, their telemetry will be mandatory and won't show in devtools/be blocked by extensions.

@kiki sure, but we'll be talking to our computers.