Allow datepicker Done button to support partial updates

[dwharrison]

In situations where existing dates are being edited by changing just one element of the date such as the year or the month, users naturally change that one element and then click on the Done button. What happens then is that because the user has not navigated back to the day level of the datepicker, the updated date is not accepted and the original date value in the model is left intact.

My suggestion is to allow (optionally?) to have the Done button accept any changes to year/month/day as the user makes them without requiring the user to navigate back "up" to the day level of the picker.

[wesleycho]

Do you mean the Close button? I can see why one might want it to update - what are your thoughts on adding a configuration value to change this behavior @icfantv? We can default to the current behavior, and it's not something that can be extended easily. I think this shouldn't be too bad to do, since we can essentially run ngModel.$setViewValue($scope.date) then close or something like that.

[dwharrison]

Yes, I meant the Close button (I keep thinking of it in terms of the default text; sorry).

[icfantv]

I'll acquiesce with the reluctance being that we have not had a request for this previously (to my knowledge) and it adds yet another API configuration for datepicker.

[wesleycho]

I am reluctant to add more configuration too, but I believe the overhead on this to be minimal.

[icfantv]

Ok. Go for it.