5 ms·
I have come to realize that these more extended elements (things beyond <select>, and input types such as password, text, or email) are actually pretty evil. Le
by IgorPartola 12y ago
I have come to realize that these more extended elements (things beyond <select>, and input types such as password, text, or email) are actually pretty evil. Let me make a small argument in favor of this view:
1. They will provide different UI across different desktop browsers/OS's, etc. The theory was that the browser can decide what the datepicker should look like. The practice is that half of them are ugly or lack the UI you want and you can't do much to fix that.
2. What the UI looks like is still in flux and will likely remain in flux. This means that not only do you have to test/support all the currently provided UI, but you also have to be ready for unexpected changes in the future.
3. Specifically because you cannot change what the (fairly complex) UI looks like, you cannot make it match your theme. This can be a huge pain.
4. There are better JS-based datepickers out there for the desktop.
The only reason to use <input type="date"> IMO would be for a mobile-only site. iOS/Safari uses a stable native date implementation which is awesome. However, on the desktop, there is no standard datepicker widget to use the same way, so it just ends up looking weird.
What I would actually love is an <input> type that lets me just type in a date (think a date of birth field) where the input is perfectly validated. That's right, in 2014 with out state of the art browsers, this is still nearly impossible. Sure you can use a regex, but have you tried putting together a regex that validates 2/29/2012 vs 2/29/2014 vs 2/29/1900? On top of that, the patter= attribute doesn't prevent you from typing/pasting, it only provides a place to put validation that's optional. A callback mechanism for as-you-type validation would be so much better.
- jimktrains2 12y ago> 1. They will provide different UI across different desktop browsers/OS's, etc. The theory was that the browser can decide what the datepicker should look like. The practice is that half of them are ugly or lack the UI you want and you can't do much to fix that. In theory they'd be more consistent across the platform, just like text and select boxes; I'm not seeing the problem. You're site doesn't need to have it's style imposed on every single control. > 2. What the UI looks like is still in flux and will likely remain in flux. This means that not only do you have to test/support all the currently provided UI, but you also have to be ready for unexpected changes in the future. Why do you care what the UI looks like? As long as the API is stable. > 3. Specifically because you cannot change what the (fairly complex) UI looks like, you cannot make it match your theme. This can be a huge pain. I count this as a plus, honestly. > 4. There are better JS-based datepickers out there for the desktop. Ugh. The less we rely on javascript for basic functionality the better. You're js, highly themed date picker probably isn't very accessible and probably doesn't function like the rest of the system does either. The more we can leverage the User Agent, the more we should. It's easier on developers. It's more accessible. It's more consistent across the user's platform.
- IgorPartola 12y ago> In theory they'd be more consistent across the platform, just like text and select boxes; I'm not seeing the problem. You're site doesn't need to have it's style imposed on every single control. I agree about the in-theory part. In practice, it has not happened. > Why do you care what the UI looks like? As long as the API is stable. I don't. The designers do. And if one of the four major browsers looks like crap, the design doesn't get scrapped, but the datepicker does. > Ugh. The less we rely on javascript for basic functionality the better. Right. Then give me a validated input field where I can say "this is a date. Don't type in anything else" and the browser makes it work. Nobody has done that yet. Basically, there is a difference between how things should work in theory and in the ideal world, and then there is the mess we deal with now and for the next 5-10 years. I'd rather have an imperfect solution that saves me developer time and gives the user a better experience, than a perfectly engineered solution where the only good thing is the API.
- jimktrains2 12y ago> I agree about the in-theory part. In practice, it has not happened. Just like text boxes and select boxes, right? Which is why everyone is trying to re-invent them too? We all know how much those are loved. > I don't. The designers do. And if one of the four major browsers looks like crap, the design doesn't get scrapped, but the datepicker does. Obviously you do care otherwise you wouldn't be having this conversation. Also, the default controls don't look crappy. > Right. Then give me a validated input field where I can say "this is a date. Don't type in anything else" and the browser makes it work. Nobody has done that yet. Then you need to educate users on what a valid date looks like. I feel that that's much harder than using a standard date control. > Basically, there is a difference between how things should work in theory and in the ideal world, and then there is the mess we deal with now and for the next 5-10 years It's only an issue because everyone seems to think having absolute control over the look of their website at the expense of usability. > I'd rather have an imperfect solution that saves me developer time and gives the user a better experience, than a perfectly engineered solution where the only good thing is the API. I have no idea what you mean. Easier for the developer and better user experience would be the built in date picker. A built-in datepicker should be following a standard API similar to every other HTML element.
- Siecje 12y agoAn 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