nasso_dev • 3 days ago

> 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.

2
dimal • 2 days ago

This is only if you opt in to base-select, so if you don't use that, everything should continue to work the same, as far as I can tell.

1 reply
Macha • 2 days ago

"You" in this case is the website author. From a user perspective, that doesn't solve the problem.

gruez • 3 days ago

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.

2 replies
johannes1234321 • 3 days ago

> 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.

asddubs • 3 days ago

you're misunderstanding, this will leave the appearance of the select on mobile up to the web developer