Date Picker not requiring to click OK

[M_Whitenight]

A user should not be required to click OK after selecting a date. I read another post where there was concern about a user selecting an incorrect date. If that occurred the user can reselect the correct date. I have had end users get frustrated because they "couldn't select a date" because they didn't realize OK has to be clicked. 

[GarryPope]

Yes, please add this. Although the action is only lifting your finger 1 centimetre and putting it back down again, it's hardly working 10 hours a day in a coal mine, haha, but our users are not keen on this. 

[sam_sonepar]

Perhaps for the fear of selecting wrong date, the app maker should have the choice between having an "OK" button or not.

The vast majority of our users are not happy about having to press "OK". They would much rather click on the date and move on to something else.

When you're job is data entry, you simply want the process to be as smooth as possible!

[techneaz]

I face the same issue with my users. The okay button is redundant here and results in wrong date selection. Users select the date and exit without pressing okay.

[Tamer66]

absolutely correct we have the same issue with our users and a lot of wrong selected dates.

[lukecwa]

This combined with the fact that the date picker UI is massively oversized and seemingly can't be modified, the majority of our users on 1080p monitors do not even see the OK button and have to scroll down. They select the date, click out of the popup and their submission fails as they didn't enter a date.

Frustrating that there's no option to fix this.

[Anonymous]

Possibly redesign the entire date picker. If using extensive dates ie Date of Birth some users do not intuitively click on the year but go back month by month, which is understandably infuriating. Separate roller style dates or just a smart fuzzy input?

[Gianluca]

1 dollar for every user asking me why the date picked is not automatically selected...

[lorraine_steven]

From an accessibility standpoint this requires additional keystrokes also.  Simplest solution would be to ensure that when the date is chosen the system automatically accepts it.  the less keystrokes required in an application the more user friendly it is from an accessibility standpoint.

[bd82]

Yes, this! I would be fine if the picker doesn't automatically close when a date is selected (so those who click the wrong date first can immediately click another), but clicking elsewhere on the canvas to close the date picker needs to change the selected date to whichever was last clicked. This is the UI convention everywhere on the web. Check out kayak.com, hotels.com, airbnb.com - in every case selecting a date does not cause the date picker to close, but clicking away from the date picker closes and saves the dates selected without clicking Apply or OK.

[BenGin]

Yep, so many end users want a date picker that does not need clicking the OK button. They wanted it so badly, I had to write my own Common Component. But there are limitations that the end users also want "Autosave" so that as soon as they change the date, it will Patch to the Database (or save locally to a Collection). To do this, I would have to enable the "Experimental" setting for "Enhanced Component Settings". However, since it is Experimental, Microsoft themselves advise not to use any of these settings in a Production environment.