[REACT] timeZone and "allDay" and adding events

[tcs-rl]

Hi,
we're starting to use the "timeZone" options currently. We've run into a few problem:

1. evens with the "allDay" property set, do not display correctly on initial load. In the example the allDay event is from 12:00 till 12:01 (so one minute long) despite this the event gets displayed across two full days. (You will need to zoom out using the mouse wheel)
2. If you repeatedly change the time zone, the event gets longer and longer, spanning an extra day with each change of the time zone. (zoom out with the mouse wheel)
3. When later on adding a new event via "scheduler.project.eventStore.add" it seems the scheduler requires the time to already converted to whatever time zone the scheduler is currently set to, otherwise it will always take the given time as "local time in the currently set time zone". Is this intended behaviour?

[joakim.l]

Hi!

Thanks for letting us know. I have created a bug issue for number 1 and 2: https://github.com/bryntum/support/issues/8703

Number 3: When the Scheduler is configured with a timeZone, all UI interactions and API add/modify etc. will treat dates as local to the configured timeZone. So yes, that is by design.

[joakim.l]

Hi

We would be very greatful if you could give us some feedback on this quite complicated case.

What would you expect from time zone converting events with allDay set to true:

1. The original startDate (and endDate), gets converted to the specified timeZone. Events will show up as 00:00-00:00 independent on what timezone it is. Depending what value the endDate has, the duration could change between x and x+1 depending on time zone (where x is the original duration in days).
2. Only the calculated startDate and endDate gets converted to the specified timeZone. Events will not show up from 00:00+y to 00:00+y (where y is the time zone offset from the local system time zone).
3. Something else?