Hi Tiago, I finally managed to reproduce this issue.
Looks like it happens in specific timezones only, that’s why I could not reproduce easily.
I’m looking into it, and get back to you with more info on this!
where startTime had the time set to 0:00. As the date arrived to the daylight saving day, it switches to 1:00, because in the Brazilian timezone the clock is forwarded at 0:00. Since the while cycle continued to add 7 days, all date objects after the daylight saving day had the time set to 1:00. This caused issues when determining the invalidity of the dates. In other timezones this was not an issue, since daylight saving usually occurs in the morning, 3:00 or 4:00 AM.
Feel free to upgrade to 4.4.3, and confirm if the issue is solved for you.
Hi Isti, now I got same error on safari. I´m disabling “w0” to flag Sunday as invalid and works fine on chrome, but in Safari is disabling Saturday.
Can you check please? Thank you
Looks like in Safari the setDate method of the Date prototype works incorrectly with the daylight saving (at least different, than in the other browsers).
I already found a different solution, which works on Safari as well, will be included in the next release.