5 ms·
I'm surprised the article doesn't talk about the <datalist> element. It makes the using the native time input much more user friendly as you can populate it wit
by dairylee 10mo ago
I'm surprised the article doesn't talk about the <datalist> element. It makes the using the native time input much more user friendly as you can populate it with common times (e.g. Every 30 minutes: 09:00, 09:30, etc... instead of allowing every minute to be selected by default)
It's not quite fully supported in browsers but it's a nice enhancement to those where it works.
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/datalist#date_and_time_types https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...
- carlosjobim 10mo ago> It makes the using the native time input much more user friendly as you can populate it with common times (e.g. Every 30 minutes: 09:00, 09:30, etc... This is a nightmare everywhere I have seen it implemented. I cannot think of any situation or use case where this is not the worst solution possible. In one system we use, you have to scroll through a 12000 pixel tall list of 15 minute increments. And you can't type to search, because they use AM/PM....
- jrochkind1 10mo agoIt does talk about datalist! Near the end. Maybe they changed the article and added it after you commented? It doesn't say a ton about it. I'm interested in hearing more about usability of actual current browser implementations of these widgets, with dataalist but also in general.