Re:Firefox 33
by IgorPartola on Tuesday October 14, 2014 @01:32PM
(#8454587)
It'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.
Re:Firefox 33
by jimktrains2 on Tuesday October 14, 2014 @02:37PM
(#8454968)
And many of those JS selects suck on mobile and limited browsers.
Re:Firefox 33
by IgorPartola on Tuesday October 14, 2014 @04:20PM
(#8455548)
Which 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.
> 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.contr...
https://developer.apple.com/library/mac/documentation/Cocoa/...
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.