Calendar does not seem to be using local timezone

[Phyks]

Hi,

I have set events in my calendar on my Android phone (using DavDroid + caldav). The events are correctly saved on my phone, with the right time, in the "UTC-4" timezone (NY timezone).

When going online on my Cozy, the events are correctly displayed, at the correct time, except they are displayed in UTC+2 timezone (Paris timezone). That is, an event at 8 o'clock tomorrow is displayed at 14.

However, my system should be correctly configured to use the NY timezone at the moment, that is

>>> new Date().getTimezoneOffset();
240

So Cozy seems to be handling correctly the various timezones in an event, but the render does not seem to make use of the user's local timezone.

[jsilvestre]

Hi @Phyks, thank you for the report. What timezone ils configured within your Cozy ? (See settings screen on the home).

Your Cozy is supposed to use this one.

Thank you,
Joseph.

[clochix]

@Phyks also there are known issues when displaying recurring events. Are your events recurring ones?

[Phyks]

Oops, indeed, I missed this setting. Currently, it is set to "Europe/Paris", that's why my whole calendar is displayed in this timezone I think.

@clochix nope, regular single events only in this particular case. I saw the other issue before posting.

@jsilvestre so maybe there should be an option to "autodetect" timezone, with a fallback default timezone for the whole cozy? Or just a popover "Hmmm, your current timezone does not match the one from your Cozy, which one do you want to use?" (and a remember cookie)?

[jsilvestre]

One problem is that many things require a timezone in Cozy, which is a why we don't auto-detect anything and it's one of the setting you define during registration.

What could be done, and I think it's what you are requested, would be to display a warning somewhere in the UI when your system's timezone doesn't match your Cozy's timezone. What do you think about it?

[Phyks]

Yes, that was this kind of thing I had in mind.

Also, is it absolutely necessary that the Cozy (server side) timezone matches the client timezone? I mean, the Cozy timezone could be used for almost everything on the server side, and Calendar could have a local timezone setting, just for display purpose?

Actually, with the current behavior, I would hesitate quite a lot before changing my timezone in the Cozy settings, because it is quite unclear for me whether this could break something or if it would just change the displayed content and actually solve the issue. Plus I had forgotten about this option at first :)

As a final note, Nextcloud's calendar, on its side, seems to be using my browser's local timezone.

[jsilvestre]

Alright, thanks! I added this feature to the backlog. I noted that there is a need to rethink how we handle timezones. Thank you for the input about what Nextcloud does, it'll save me time at some point!