BUG -- Time hours and minutes only showing "01:**"

Scheduler Javascript
#1

This is a problem on all of the demos as well as the most recent (2.3) version.

To recreate - click an event and click the calendar icon so you can see the details and adjust the time. Click the selection box for the hour. It starts at 00:00 up to 01:55, then recycles to 01:00 again. It does this repeatedly for all hours.

I’ve confirmed this with multiple computers/operating systems/browsers hitting the demos, so it isn’t anything I could have done.

Thank you,
Rob

#2

Adding a screenshot. Note that the hour doesn’t change after the minutes reach 55…

Also - this is from the “Basic sample”, so it isn’t a “customization” issue.

hour_bug.gif820×694 182 KB

#3

Which timezone is set on the problematic PC?
The issue can’t be reconstructed from our side, and so far there were no similar reports as well.

#4

It was multiple PCs. One was a Windows 7 box, the other a Centos 5.5 box. Both are set to Eastern time (America/ New_York).

The problem appears to have gone away. Could it have been related to the shift to Daylight time?? I don’t think it started before yesterday and yesterday was the day of the shift. And that would make sense - it counted up properly until 2:00 am, then at 2:00, it shifted back an hour and got stuck in the 1:00 hour.

Thank you,
Rob

#5

Could it have been related to the shift to Daylight time??
Yep, most probably it is related to daylight time settings.
We will doublecheck it locally, to prevent such issue in a future.

#6

Hello, Rob.

Thank you again for your valuable feedback. :slight_smile:
We were able to reproduce this issue and fix it. This issue should be resolved in the upcoming version.

Best regards,
Ilya

#7

Ilya,

Thank you for the prompt reply.

I noticed something else, though. This was the Spring daylight time shift. So, if it was related to the shift to daylight time, it should have sprung forward an hour, not back, so this behavior shouldn’t have happened at all. (It would more likely have occured back in November.)

Thank you again,
Rob

#8

Hello, Rob.

It was indeed related to the time shift.

This is just a matter of how exactly it worked incorrectly :blush:
I’ve attached screenshot of select during timeshift (fixed).

Thanks again.

Best regards,
Ilya