Changing a calender event from all day uses wrong time zone with Google calendar
Categories
(Calendar :: Calendar Frontend, defect)
Tracking
(thunderbird_esr91 affected, thunderbird97 affected, thunderbird98 affected)
People
(Reporter: bugzilla, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0
Steps to reproduce:
- Create a new calendar event. I tested using Google calendar.
- Set it to "All day event".
- Save it.
- In the main calendar view, double click on it to edit it again.
- Uncheck "All day event".
- Notice that the time zones shown for the start and end times are the local time zones.
- Save it without changing the time zones.
- In the main calendar view, double click on it to edit it again.
- Notice that the time zones shown are now UTC, which is not what was selected.
Actual results:
The start and end time zones are set to UTC, not the local time zone.
Expected results:
The local time zone should have been used.
Comment 1•4 years ago
|
||
Alistair, can you still re-produce the issue with a Thunderbird 91 release version or a recent Thunderbird beta/daily?
| Reporter | ||
Comment 2•4 years ago
|
||
Yes, this still happens on Thunderbird 91.1.2 on Ubuntu 21.10.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
I observe the same issue in Thunderbird v91.5.0 and beta v97.0b3 using Windows.
I was going to file a bug showing the following steps to reproduce:
Note: My computer and calendar are configured for USA Pacific time zone (America/Los Angeles).
(1) Add an existing Google Calendar to Thunderbird using CalDAV URL such as
https://apidata.googleusercontent.com/caldav/v2/xxxxxxxxxxxx@group.calendar.google.com/events
(2) Create and save an all-day event
(3) Edit the event: disable all-day setting and specify a start time.
(4) Observe: The saved event time doesn't match what was specified. (Maybe saved as UTC time.)
Bug still exists. Also happens to me. Changing from all day to 12:00 displays 14:00 (UTC +2).
I already missed an important appointment because of the wrong time.
Comment 7•3 years ago
|
||
Is this also seen in version 102?
Updated•3 years ago
|
| Reporter | ||
Comment 8•3 years ago
|
||
102.3.1 appears to work correctly. In step 9, the time zone is the local time zone.
Comment 9•3 years ago
|
||
Resolving as WORKSFORME per comment#8.
Description
•