3 ms·
In the 21st century, every date picker should be able to accept both mouse and keyboard input and be very permissive about what is allowed. There should be a t
by shadowgovt 4y ago
In the 21st century, every date picker should be able to accept both mouse and keyboard input and be very permissive about what is allowed.
There should be a text box I can just type "January 1 2022" or "2022-1-1" or "4/20/69" into, and it just figures it out (with a disambiguation dialog and 'save as default' popped if I feed it something ambiguous).
- dclowd9901 4y agoBut that’s exactly the problem. A good website employs an “international-first” approach. As such, having such lenient formatting can be a compounding problem pretty quickly as you’re trying to accommodate all types of formatting dates for all languages and regions. Imo, the site to plainly and explicitly require an exact type of date formatting. It’s very easy to validate and they can even help with formatting.
- shadowgovt 4y agoThe site shouldn't have to do any of that. Ideally, the client-side date picker should handle it (it has the context to know user preference on whether "4-1-69" means January 4 or April 1, and the context to know to ask for clarification if it doesn't know the user's preference yet).