3 ms·
An ideal implementation would allow you to customize the look with CSS. You recommend using a JS-based datepicker, what would the difference be? This would be
by Siecje 12y ago
An ideal implementation would allow you to customize the look with CSS.
You recommend using a JS-based datepicker, what would the difference be?
This would be faster and easier since you don't have to keep the JS-based one up to date.
- IgorPartola 12y agoIt's not just CSS, though that's a part of it. What if you want to customize labels? How about error placement? Behavior when you click outside of the widget? More complex open/close interactions? Even a simple <select> gets re-implemented every so often (chosen.js) because it's use cases are too complex for what it can do. A date picker is so much more complex than that.
- jimktrains2 12y agoAnd many of those JS selects suck on mobile and limited browsers.
- IgorPartola 12y agoWhich is why my complaint is about the desktop. As I mentioned, on mobile the widget actually works correctly: it looks like a native OS datepicker. Native OS datepickers do not exist on the desktop: not in the browser, not anywhere else, unless you count the Windows clock dialog.
- acdha 12y ago> Native OS datepickers do not exist on the desktop: not in the browser, not anywhere else, unless you count the Windows clock dialog. Their existence is why this is such a popular browser feature request: http://msdn.microsoft.com/en-us/library/system.windows.controls.datepicker%28v=vs.110%29.aspx http://msdn.microsoft.com/en-us/library/system.windows.contr... https://developer.apple.com/library/mac/documentation/Cocoa/Reference/ApplicationKit/Classes/NSDatePicker_Class/Reference/Reference.html https://developer.apple.com/library/mac/documentation/Cocoa/... https://developer.gnome.org/gtk3/stable/GtkCalendar.html https://developer.gnome.org/gtk3/stable/GtkCalendar.html