←back to thread

The <select> element can now be customized with CSS

(developer.chrome.com)
507 points tosh | 1 comments | 31 Mar 25 09:11 UTC | HN request time: 0.211s | source
Show context
wolframhempel ◴[31 Mar 25 15:14 UTC] No.43535984[source]▶
The fact that I'm disproportionally excited about this probably dates me as an early 2000s web developer. But since selects can do things that you simply cannot recreate in HTML, e.g. have options drop downs that extend outside the viewport boundaries, makes this a really helpful feature.

Now, do autocompletes and tag selectors next...

replies(6): >>43536012 #>>43536059 #>>43536090 #>>43537120 #>>43537585 #>>43539203 #
preisschild ◴[31 Mar 25 16:52 UTC] No.43537120[source]▶
<input type="datetime-local"> with automatic ISO8601 timezone offsets would be awesome too!
replies(1): >>43540196 #
sublinear ◴[31 Mar 25 21:29 UTC] No.43540196[source]▶
ISO-8601 is not the correct format for serializing local time unless it's in the past.

In my experience, a local datetime picker is going to be used almost exclusively for a future date and time. What you want instead of a timezone offset is a zone ID. That way date and tzdata can handle it properly on the backend.

replies(2): >>43540867 #>>43543181 #
1. ibejoeb ◴[01 Apr 25 05:35 UTC] No.43543181[source]▶
Right. The offset is not enough without a reference recorded time. You need the time and the time zone in order know the true time. This is a big problem is systems that don't have an intrinsic time type that deploy and have a database full of ambiguous times. Once it happens, backfilling that is a real slog.