2 ms·
I'd hate to see this become the standard. The build-in browser datepicker is utter shit. There's a reason nobody uses it. Frankly the whole HTML form spec is a
by blacktriangle 6y ago
I'd hate to see this become the standard. The build-in browser datepicker is utter shit. There's a reason nobody uses it. Frankly the whole HTML form spec is a world of crap for what users are expecting from UIs these days. Being legally limited to what the WHATWG manages to agree on and ship in a browser would be a huge step back for web applications.
- iudqnolq 6y agoThe default is hard to use. However, I've found it better than the open-source alternatives I've seen (mainly AirBnB datepicker) if you test across {Chrome,Firefox}{Desktop,Mobile}. I also wasn't suggesting the built-in should be mandated, just that if you replace it you either provide a way to downgrade to the built-in or make your replacement at least as accessibile. If you make your replacement usable with only a keyboard you'll be nearly there anyway.
- TheCoelacanth 6y agoAny half-decent datepicker library is going to be accessible. If you absolutely must reinvent the wheel, then yes, you will need to put in a bit of extra effort to make it accessible.