←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.205s | source
Show context
nasso_dev ◴[31 Mar 25 14:19 UTC] No.43535363[source]▶
> It doesn't trigger built-in mobile operating system components.

I worry about this. The built-in mobile operating system components are reliable, accessible, and responsive. I really like it when an input element opens the Android UI because I know how it works and that it is reliable. This applies to <select>, but also date/time inputs for example.

replies(2): >>43535417 #>>43539290 #
gruez ◴[31 Mar 25 14:23 UTC] No.43535417[source]▶
Chrome already uses plenty of non-native components. Firefox is similar. Moreover while I can understand the concern about poorly implemented components from random web developers, Google is probably the best positioned to implement a widget that faithfully replicates the native equivalent, at least on Android.
replies(2): >>43536132 #>>43536737 #
1. johannes1234321 ◴[31 Mar 25 16:19 UTC] No.43536737[source]▶
> Chrome already uses plenty of non-native components. Firefox is similar.

This is then won't be consistent with native OS apps, but still be consistent across websites. Better than everybody doing different div+JavaScript magic which behaves slightly different across different websites.