Scheduler with timezone displays incorrect current time

[austinw-fineart]

Bug report

Scheduler's timezone is not regarded for highlighting the current day in Scheduler views. Instead, the current day is highlighted based on local machine timezone. The issue becomes obvious on setting currentTimeMarker.useLocalTimezone to false and having Scheduler with timezone already on a different date, compared to local machine timezone, e.g. local timezone on your computer to (UTC +12:00) Auckland, Wellington and Scheduler timezone: "Pacific/Honolulu", // (UTC -10:00) Hawaii

Description of users' issue: "The current time marker can be set to use the scheduler timezone. However, on week and month views, the highlighted column representing the current day of the week uses the local timezone. It's rather confusing to read the current time marker with the wrong day highlighted on week views. In addition, the current highlighted day is also incorrect on the attached calendar widget."

Reproduction of the problem

1. Use the following Dojo snippet with Scheduler with timezone set (ie. "Pacific/Honolulu") - UTC -10:00 and currentTimeMarker.useLocalTimezone = false
2. Set timezone of your machine to (UTC +12:00) Auckland, Wellington
3. Check day/week/month/timeline view

Current behavior

• Current time marker shows the current time based on Scheduler's timezone - this is Expected.
• Highlighted day (having class k-today) for today in all views is based on the timezone set on the local machine, instead of Scheduler's timezone.
• The date highlighted in the calendar as today is based on the timezone set on the local machine, instead of Scheduler's timezone.
• NOTE: Pressing Today button in Day view used to navigate also to the day based on the timezone set on the local machine, instead of Scheduler's timezone. This behavior was fixed with the following issue.

Expected/desired behavior

Ideally, the highlighted date should respect the current time marker setting. - Such behavior would also be confusing, as the current time marker setting is designed to control only the current time marker.

• If there is Scheduler timezone defined, k-today should be applied to the the current day based on Scheduler's timezone. The calendar day marked as today should be based on Scheduler's timezone.
• If there is NO Scheduler timezone defined, k-today should be applied to the the current day based on local machine's timezone. The calendar day marked as today should be based on local machine's timezone.

Environment

• Kendo UI version: 2019.3.1023
• Browser: all

[Dimitar-Goshev]

@austinw-fineart Thank you for reporting this issue. I added some clarifications on its reproduction and expected vs current behavior.

[montella1507]

We have left Kendo Scheduler because we havent found any way how to solve this issue...

Why you just havent provided an option how to KEEP dates as they are??? Its is really pain, specially with your semi-custom timezone-names...

please just allow programmers to use "NEVER EVER MODIFY datetimes"..

I really HAD to datevalue - new Date().getTimezoneOffset()...

Transforming value for scheduler is not good idea - specially if you are able to define custom component templates...

You pass 9:00 UTC as input - your browser have UTC+2 and what is result if you use

inputDate | date in angular?

UTC + 4.... (Scheduler adds 2 hours and 2 hours adds DATE Pipe corectly) Why... Please, provide a way how to tell Scheduler NOT TO recalculate events data... Timezones are something that should be modyfing on Outputs (eg. formatting).

[nelito987]

Reported in ticket ID: 1606060