Bug 119175 - <input type="date"> doesn't show any date-specific controls
Summary: <input type="date"> doesn't show any date-specific controls
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: http://www.wufoo.com/html5/types/4-da...
Keywords: InRadar
Depends on: 214946 215155 215938
Blocks: 209389
  Show dependency treegraph
Reported: 2013-07-27 00:23 PDT by Antoine Quint
Modified: 2023-09-04 19:17 PDT (History)
30 users (show)

See Also:

rendering in Safari, firefox, chrome (176.84 KB, image/png)
2023-09-04 19:17 PDT, Karl Dubost
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antoine Quint 2013-07-27 00:23:12 PDT
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.
Comment 1 Radar WebKit Bug Importer 2013-07-27 00:23:51 PDT
Comment 2 Sebastiaan Lokhorst 2017-01-04 14:22:28 PST
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?
Comment 3 m.kurz+webkitbugs 2017-01-09 01:33:30 PST
Is there a chance we'll see this in Safari on macOS soon?
Comment 4 m.kurz+webkitbugs 2017-03-08 01:36:34 PST
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
Comment 5 Sebastiaan Lokhorst 2017-11-14 07:40:18 PST
This just landed in the stable Firefox 57.

Unfortunately still nothing in Safari 11.
Comment 6 p.scheit 2018-10-21 06:27:51 PDT
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!
Comment 7 Dayton Lowell 2018-11-07 10:48:54 PST
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
Comment 8 Kris 2019-01-21 17:38:12 PST
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.
Comment 9 Martin Häcker 2019-01-21 23:15:13 PST
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?)
Comment 10 kempfjj 2019-02-08 06:03:15 PST
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?
Comment 11 Cagdas Tulek 2019-05-09 18:04:10 PDT
Any chance to prioritize this feature or any explanation why it does not get priority?

Comment 12 Sander 2019-10-29 08:10:24 PDT
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?
Comment 13 aislinn.m.b.hayes 2020-01-17 05:58:41 PST
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
Comment 14 Ben Frain 2020-02-16 10:02:46 PST
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
Comment 15 Robert Bradford 2020-06-24 16:17:03 PDT
Are there any updates on this one?
Comment 16 Martin Häcker 2020-06-25 01:38:41 PDT
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.
Comment 17 Jay 2020-07-21 09:21:43 PDT
I would also like this to be implemented!
Comment 18 Aditya Keerthi 2020-08-24 12:13:03 PDT
Note: This work is being done in subtasks.
Comment 19 Roman A. 2020-09-19 12:56:23 PDT
Aditya Keerthi Please confirm that 'done' button also added to mobile picker version.
Comment 20 m.kurz+webkitbugs 2020-10-23 11:39:26 PDT
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
Comment 21 Sam Sneddon [:gsnedders] 2022-06-14 08:55:06 PDT
Shipped last year in April.
Comment 22 Karl Dubost 2023-09-04 19:17:46 PDT
Created attachment 467547 [details]
rendering in Safari, firefox, chrome

as I was confused.