You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 29, 2019. It is now read-only.
The PR makes it clear you don't want to accept arbitrary strings that the browser interprets as a date using new Date().
I'm getting dates from a web service in this format. It seems this would be fairly common. It seems to me you should be able to handle this particular format.
Problem is that different browsers will even handle ISO dates in different and unexpected ways - it also overly complicated the model-view interplay with ng-model. The best workaround on the user's side is to convert it to a date object before binding to the model - for any properly built application, this should be a trivial change since there should always be a parsing layer that converts the api response before binding to a model.
The date picker no longer validates when it is passed an ISO date string.
Plunk
This is a consequence of #4062.
The text was updated successfully, but these errors were encountered: