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.
I came across the same problem today. Seems to me, that the baseDate used in dateparser.js, line 130, is supposed to be a date object. If you enter the date manually however it is a string, so the call
Created a plunkr.
The date is initially set as string. A manual edit in the input box triggers the error. If you select a date via the picker or initialize mydate with new Date() everything works fine.
@ChristophT, @wesleycho The datepicker has these open PRs: #3759, #3691, #3682, #3344, #2513, #2369, #2142 that are related to how the date is parsed. I updated the plunk with the latest build from the master branch so we can test against that.
Hi,
If I manually (via the textbox) set the date back a year
i.e. change 2015 to 2014
then the control shows as invalid (i.e. a red border)
Is there a fix for this?
The text was updated successfully, but these errors were encountered: