Scheduler view in UTC while data in another timezone and crossing daylight savings

[Scott]

Not sure if this is a bug or my bad configuration:

http://dojo.telerik.com/uTAHe

I have set up a recurring event that crosses the Australia/Sydney daylight savings time.

I think I have set the scheduler and data source to view events in UTC, but the event does not display back an hour. When I change the data source to use Sydney's time the event display is correct. 

Is there something that I have missed or have incorrectly configured in my example?

[Ivan Danchev]

Hello Scott,

By setting the data source's timezone to 'Australia/Sydney' you override the timezone set to the Scheduler and the event is shown as if the Scheduler's timezone is set to 'Australia/Sydney'. So could you elaborate more on the difference between how the event is actually displayed (starting at 03:00 AM Sat 1 April) with both options set to 'UTC' and the way it should be displayed?

Regards,
Ivan Danchev
Progress Telerik

[Scott]

Hello Ivan,

I have updated my example to hopefully make it clearer what I mean: http://dojo.telerik.com/uTAHe/4

I have removed the redundant timezone set on the scheduler to avoid confusion. The datasource in my example is set to UTC, but the data inside it has the startTimezone and endTimezone override set to Sydney. I have set it up this way as I am parsing an iCalendar file with different timezones set.

The second occurrence for Test1 should appear at 2am when viewed from UTC time. I think this is a bug where the timezone offset is used from the first event and not calculated on each recurrence.

Looking at the source code of v2017.1.118 kendo.scheduler.recurrence.js, should line 887 in the expand function account for changing zones instead of using the eventStartMS?

Regards, Scott

[Ivan Danchev]

Hello Scott,

Thank you for the additional information provided. The dev team has fixed several timezone related issues so I checked your example with the latest internal build (2017.3.801) and there was an hour of difference between Test1's second occurrence and Test2. The fix should be included in the official version in the next release.

Regards,
Ivan Danchev
Progress Telerik

[Scott]

Thank you Ivan. I will check again once when the next release is available.

[Scott]

I have checked the 2017 R3 release and the bug has been fixed. Cheers!