2 ms·
The problem is that the web didn't make the right separation between form fields (the composite values you submit) and the actual user facing widgets you use to
by Spivak 4y ago
The problem is that the web didn't make the right separation between form fields (the composite values you submit) and the actual user facing widgets you use to produce those values.
I want to be able to do things like
<input type=date widget="calendarpicker">
<input type=date widget="mmddyypicker">
<input type=date widget="mycustomcomponent">
so you're stuck with not great UX if the platform-specific picker sucks for your use-case which for this is absolutely does. If you're born in 1950 on iOS have fun spinning the year wheel for a while instead of just typing in the number.