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 use datepicker and i'm trying to type date using keyboard. The specified format for datetimepicker is yyyy-MM-dd. When i type whole data it works correct. when i tries to change for examle month it starts to fail.
The path to the bug looks like this:
I have correct date in my datetimepicker for example 2015-07-14
I whant to change it to 2015-08-14 so i start editing it and im removing 7 - i have 2015-0-14 writen in my datetimepicker. The validation shows me that it is not correct date ant this is fine for me
3.I type 8 and i have 2015-08-14 in my datetimepicker. The validation message still shows up...
There is a screen from my debuger -
You can notice that houres, minutes and seconds have NaN values. The bug is easy to correct.
I edited this piece of code
i replace this :
if ( isValid(fields.year, fields.month, fields.date) ) {
dt = new Date(fields.year, fields.month, fields.date, fields.hours, fields.minutes, fields.seconds,
fields.milliseconds || 0);
}
with:
I use datepicker and i'm trying to type date using keyboard. The specified format for datetimepicker is yyyy-MM-dd. When i type whole data it works correct. when i tries to change for examle month it starts to fail.
The path to the bug looks like this:
3.I type 8 and i have 2015-08-14 in my datetimepicker. The validation message still shows up...
There is a screen from my debuger -
You can notice that houres, minutes and seconds have NaN values. The bug is easy to correct.
I edited this piece of code
i replace this :
if ( isValid(fields.year, fields.month, fields.date) ) {
dt = new Date(fields.year, fields.month, fields.date, fields.hours, fields.minutes, fields.seconds,
fields.milliseconds || 0);
}
with:
The text was updated successfully, but these errors were encountered: