| ▲ | silvestrov an hour ago | |
date pickers are something that quickly gets overly complex and site specific. They are only simple when you have no restrictions on which dates that can be selected. But a date picker for a hotel, airplane travel, restaurant, ... might have to show some days as disabled or some days that are "cheap offer" dates. To this add anything that needs to select an interval, like an airplane return ticket. | ||
| ▲ | Narretz a few seconds ago | parent | next [-] | |
that's true. But even for some of the easiest cases some browsers don't support them. input[type=month] for example still has no custom UI in Firefox or Safari. And Chrome has had one for 14 years! | ||
| ▲ | xnorswap an hour ago | parent | prev | next [-] | |
And then there's the nightmare of any interval that runs over daylight savings boundaries, and what that really means if you want not just a date-picker but date/time picker. | ||
| ▲ | troupo 41 minutes ago | parent | prev [-] | |
> date pickers are something that quickly gets overly complex and site specific. I'd settle for a browser specific picker that works in 80-90% of use cases. Instead it took browser several years after introudcing type=date to make a datepicker that is actually usable, and not a throwaway tiny design cooked up by an underpaid intern | ||