Also adding that internationalization, IIRC, for native date input on the desktop is entirely based on the browser locale. That's neither user friendly nor dev

Also adding that internationalization, IIRC, for native date input on the desktop is entirely based on the browser locale. That's neither user friendly nor developer friendly. It just sucks. Can i18n become a real concern for specs anytime soon? The non-US world at large would be grateful. In fact, these HTML5 form features have just basically fragmented the development of mobile and desktop web pages. If we're gonna have different sets of features for different platforms, that's fine. Just be clear about on the api level. It was better when the date input was not even implemented on the desktop, at least we could detect it and shim accordingly, now it's basically a false positive since it's implemented without any real effort.