[greggturkington]

Not gone, but that's the direction we're heading (hopefully).

> it may currently still be best to use a framework or library to present these, or to use a custom input of your own. Another option is to use separate date and time inputs, each of which is more widely supported than datetime-local

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/in...

[onli]

I literally waited years for this. This year I opted to change a backend date input from datetime-local to date and time input input fields, after waiting too long for browser support. The datetime-local field got added 2014, "browsers will support it soon"...

[exyi]

> Because of the limited browser support

Which browser does not support it (if we can exclude IE 11)? And if some obscure browser does not support, it will just fallback to input[type=text], so no big deal. I'm really looking forward to get rid of all these JS implementations which can't properly handle keyboard / touch / screenreader / whatever comes.

[he_is_legend]

1 year old safari. it was added april 2020 - https://caniuse.com/?search=datetime-local