Bug 119175

<rdar://problem/14567780>

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 datalist 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? Thanks.

Opera implemented this in 2009 (10 years ago!). Chrome in 2012. Edge in 2015. Firefox in 2017. Safari on iOS supports this since 2012. When will Safari on MacOS finally follow?

This is a big issue not just for browser compatibility but for accessibility as well. The native date picker is fairly accessible and is a good option for developers not wishing to build their own date-pickers, but lack of support for a major browser like Safari is a huge problem - especially given that VoiceOver is a screenreader best designed for use with Safari. For those looking for a potential solution, https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/datepicker-dialog.html is an option that has good accessibility (even better than native, given that in the native option a screenreader user can't navigate to the calendar at all - which is compliant but still not great). Unfortunately the Material UI option isn't accessible either (https://material-ui.com/components/pickers/#material-ui-pickers), and neither is the polyfill mentioned above (https://github.com/liorwohl/html5-simple-date-input-polyfill). I'm no expert but just some simple keyboard navigation testing with VoiceOver demonstrates how unusable these are... Please save me the hassle of having to build my own component and just give Safari native support :D

Updating a book I've written on HTML5/CSS3. First edition was written 2012, 2nd edition 2015. It's on the 3rd edition now and each time I write a new edition, I come back here thinking "Surely I won't have to add that paragraph explaining that there's no support in Safari". Seems sadly I do. C'mon managers who get resource for the Safari/WebKit engineers, give them what they need to get these kinds of things implemented. Despite the strides Safari has taken with privacy (thank you), it lags behind in web features that make it hard to recommend to average users. A native date/time picker would mean devs don't need to load in JS libraries for the task

Are there any updates on this one?

I am pretty sure that there is a fuckup, in that the right person from apple is not subscribed to this bug and therefore this is falling through the cracks. However I have no idea who that right person to add would be. If anyone can bring some expertise here that would be greatly appreciated.

I would also like this to be implemented!

Note: This work is being done in subtasks.

Aditya Keerthi Please confirm that 'done' button also added to mobile picker version.

Also see Bug 214946 (duplicate?) Starting with Safari TP 115, released on Oct 22, 2020, UIs for `date`, `datetime-local` and `time` are supported on macOS and iOS. The month input type is unsupported on macOS, but works on iOS. The week input type is unsupported on macOS and iOS. There will be an entry in https://webkit.org/status/ soon: https://bugs.webkit.org/attachment.cgi?id=412182&action=diff

Shipped last year in April.

Created attachment 467547 [details] rendering in Safari, firefox, chrome as I was confused.