It seems there's a regression for <input type="date"> where we don't show any specific controls to change the date. For instance, Safari 5.1.9 on OS X 10.6.8 shows a stepping control to the right of the input on http://www.wufoo.com/html5/types/4-date.html, but shows no such control in Safari 6.0.5 on OS X 10.8.4.
There still is no UI for date input in Safari 10 on macOS.
With Firefox finishing up support, Safari on macOS will be the only modern browser without support. This is a shame since Safari was one of the first to offer this on iOS.
Is there a chance we'll see this in Safari on macOS?
Is there a chance we'll see this in Safari on macOS soon?
Can someone please give an update on this issue?
With Firefox 54 having date inputs behind a flag soon Safari will be the last major browser left lacking support for it. See http://caniuse.com/#feat=input-datetime
This just landed in the stable Firefox 57.
Unfortunately still nothing in Safari 11.
This Bug was reported in 2013 and is still not triaged?
Why is this available in mobile Chrome, but not on desktop?
Safari is becoming the only browser where polyfills are needed.
Cmon, its pending 5 years!
Safari has been adding tons of support for various form controls types and features recently:
inputmode attribute support
color input type
It's been really great to see.
That being said, Safari is the only modern browser remaining without support for the date input type. https://caniuse.com/#search=date
To my fellow web developers, here is a polyfill for Safari support. https://github.com/liorwohl/html5-simple-date-input-polyfill
Anything on this? Chrome has had a native date picker since 2012. Firefox since 2017.
Safari is the only modern browser without it. You're holding everyone else back.
This! It's super annoying to have to polypill this for even the simplest of applications where a native date picker would be well enough.
Is there a timeline on this somewhere? https://webkit.org/status/#?search=date doesn't seem to have it.
Any word from the devs where this is going?
Are there devs missing from the CC? Is this somehow falling through the cracks? (Does anyone know?)
I recently opened a bug for this in Safari as well, which was promptly closed as a duplicate.
If this doesn't happen upstream, I don't see Safari ever implementing. Is there some way I can help in getting this more visibility?
Any chance to prioritize this feature or any explanation why it does not get priority?