Hacker News Reader

Comment by jonathanhefner | Hacker News Reader

Disappointing... still no support for HTML5 date and time input types. Safari seems to be the last major hold out[0] keeping JavaScript-powered date pickers a (prudent) necessity.

[0]: https://caniuse.com/#feat=input-datetime

View on HN

Those native interfaces look so dull and out of place when having other input 'helpers' such as better 'select' with bootstrap themes, that I don't even consider them as existent and other third party date pickers are going to be around for quite a while.

Input type 'number' also gives you weird step helper which most of the time is unnecessary and there isn't even a simple way to disable it.

Somehow HTML stopped innovating for so long, the latest revision (HTML5) is just mostly fixing what sucked with HTML4 and adding stuff other third parties already did better.

Those JS pickers are going to be needed for a long time still, because native widgets are a nightmare to style consistently. Apparently nothing has been learned from the <select> styling minefield of the past.

I don't think that everyone should be able to edit the style of native elements. I prefer a consistent behavior, and the select itself works fine everywhere for example.

But i sadly agree, JS stuff is going to be needed for a long time.

There are good arguments for styling native elements and against them. I don't think this is specific to the web, cross-platform GUI toolkits have had this challenge forever.

The current datepickers on the desktop are "consistent in the same browser across many sites". There is no native solution for "consistent in the same site across browsers", which makes a lot of designers and PHBs upset, doesn't always fit the overall look of the site, and makes it harder for developers because each browser brings its own quirks with formatting, localization, validation, etc.

Reply on news.ycombinator.com