Hi there, thanks for this. This has been discussed in a few places. (I see you've participated in some!)
First, we just merged a documentation improvement in #33113.
Some more recent updates in this forum thread and this mailing list thread.
Quoting from the first link:
The consensus has been that each time it’s been looked at the cross browser support wasn’t there, and we weren’t sure about handling migrations for folks who’ve already done other things. But pending the first improving, likely the second could be addressed. (So question is largely, when, if ever, is it good enough? E.g. Is input type="date" ready for use in accessible websites? - Hassell Inclusion)
So, I'll mark this as a duplicate of #21470 and #33100. However if you have an interest in pursuing this, I would suggest a forum thread (focused on date/time) to address these points:
- demonstrate that cross-browser support is ready
- demonstrate that accessibility will be good enough, taking into account the improvements we just made to the existing widgets in #36459 and #36458.
- mention touch-friendly aspect
- backwards-compatibility concerns, especially for less common formats
- respond to any points from those earlier threads
If you can refresh this discussion, that will be a huge help. Once there is consensus to do something we can reopen the ticket. Thanks.