←back to thread

503 points tosh | 1 comments | | HN request time: 0.201s | source
Show context
wolframhempel ◴[] 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 #
asddubs ◴[] No.43536090[source]

I doubt it'll still be able to do those things. From the article:

>Using base-select loses a number of features and behaviors:

> The <select> doesn't render outside the browser pane.

> It doesn't trigger built-in mobile operating system components.

I have mixed feelings about it. Mobile users, get ready for poorly optimized select elements. On the other hand it reduces the need for javascript for styling forms, which is good

replies(5): >>43536161 #>>43537035 #>>43537996 #>>43539933 #>>43541655 #
cush ◴[] No.43537996[source]

> The <select> doesn't render outside the browser pane. ... It doesn't trigger built-in mobile operating system components.

To me, this is intrinsically what makes a <select> a <select>. Styling is great, but without these features, this doesn't really bring anything new to the table

replies(2): >>43540709 #>>43543249 #
1. wruza ◴[] No.43543249[source]

With these features scammers will create all sorts of "you have to log into your password manager" popups again.