Closed
Bug 1331239
Opened 8 years ago
Closed 8 years ago
Google Calendar Provider: Support for Timezone VTIMEZONE
Categories
(Calendar :: Provider: GData, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: anton.bugs, Unassigned)
Details
(Whiteboard: [timezone])
Attachments
(1 file)
37.51 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Steps to reproduce:
I received a meeting invite with a different timezone with the following headers:
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:SE Asia Standard Time
BEGIN:STANDARD
DTSTART:16010101T000000
TZOFFSETFROM:+0700
TZOFFSETTO:+0700
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T000000
TZOFFSETFROM:+0700
TZOFFSETTO:+0700
END:DAYLIGHT
END:VTIMEZONE
Actual results:
My local timezone is GMT+8 and it is configured correctly, however after I accepted an invite and checked google calendar (via calendar.google.com) the timezone was not changed (still +8). You can verify it by visiting the web application and clicking on more details -> [date]
Expected results:
The proper timezone (GMT+7) should have been propagated
Comment 1•8 years ago
|
||
Do you have calendar.icaljs in the advanced prferences enabled or disabled?
Whiteboard: [timezone]
Reporter | ||
Comment 2•8 years ago
|
||
it is the default value which is "false".
Comment 3•8 years ago
|
||
That timezone maps into Asia/Bangkok. Can you enable calendar.debug.log and calendar.debug.log.verbose and check what happens when you accept the event? Does it send the event with Asia/Bangkok, or with a different timezone?
Flags: needinfo?(anton.bugs)
Reporter | ||
Comment 4•8 years ago
|
||
Hi, thank you for follow up on this.
Unfortunately, I'm no longer able to reproduce the bug.
I still have the original email, and tried to accepted it. It seems propagates +7 timezone to the calendar properly..
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(anton.bugs)
Resolution: --- → INVALID
Comment 5•8 years ago
|
||
Thanks for the update, glad it works!
You need to log in
before you can comment on or make changes to this bug.
Description
•