TimeZone

[wintega]

Hi!

I’m using vkurko/calendar in a production scheduling system for coaches and ran into a timezone model issue.

Calendar events are provided in the application (coach) timezone, but the calendar itself always operates in the browser/device timezone. Because of this, when a coach is in a different timezone than the user’s device, the grid and nowIndicator become inconsistent with the actual event times.

I saw that timezone support was discussed some time ago, but I wanted to ask if anything has changed since then.

Even a minimal solution would help a lot, for example:

• a timeZone option (Europe/Amsterdam), or
• a simple offset option (e.g. minutes from UTC) applied internally when rendering slots and the now indicator.

At the moment, the only safe workaround is disabling nowIndicator, which avoids misleading UI but doesn’t solve the root problem.

Just wanted to share real-world usage feedback and ask if timezone support is something you’d consider.

Thanks for the great library!

[vkurko]

Related #576 #502 #367

The short answer is that time zone support will appear when Temporal is widely available.

Workarounds:

1. For events - simply convert the times yourself before passing the data to the calendar.
2. For nowIndicator - unfortunately no workaround, perhaps I can implement some kind of offset.

I will also consider using Temporal polyfill.

[wintega]

Thanks for the clarification — that fully makes sense.

In our case, all events are already converted on the backend and passed to the calendar in the user's timezone, so event rendering itself works well.

The only remaining inconsistencies are:

highlighting of the current day (based on device timezone)

nowIndicator, which also reflects device time

Disabling nowIndicator is currently the safest workaround on our side.

If at some point it becomes possible to pass a simple timezone offset (e.g. minutes from UTC) to the calendar for internal calculations, that would fully solve these issues without requiring full timezone support.

Thanks again for maintaining the library )))

[vkurko]

I think now is what we are looking for.

[vkurko]

timeZone option is available since v5.7.0.

[wintega]

Good afternoon! Thank you very much, it helped a lot, I returned the nowIndicator timestamp to users where the timezone did not match. Thanks again.