1292182 - Accepting Invitation from Webex/Outlook Shows Wrong Start/End Time

Status: RESOLVED INCOMPLETE

(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)

Description

[Karl Rossing]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Steps to reproduce:

Create a new invitation in webex in a different timezone (Pacific). I think the creator is using an outlook plugin to do this.  I have tested with TB 45 and TB 47 Beta


Actual results:

After the invitation is accepted, the start/end times are in the senders timezone (Pacific) and not Central Time.

Comment 1

[Karl Rossing]

Here is a sanitized version of the invite

BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 10.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Pacific Time
BEGIN:STANDARD
DTSTART:20141101T020000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:Standard Time
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20140301T020000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:Daylight Savings Time
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ATTENDEE; ATTENDEE
DTSTART;TZID="Pacific Time":20160804T110000
DTEND;TZID="Pacific Time":20160804T120000
LOCATION: Location
TRANSP:OPAQUE
SEQUENCE:1470266290
UID:94d4491c-00b0-4c51-8556-c039b060531d
DTSTAMP:20160804T180000Z
DESCRIPTION: Description
SUMMARY:Summary
PRIORITY:5
CLASS:PUBLIC
BEGIN:VALARM
TRIGGER:-PT5M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR

Comment 2

[Philipp Kewisch [:Fallen][📱📆]]

Can you specify where the timezones are misrepresented?

Comment 3

[Karl Rossing]

I'm in central time timezone

Comment 4

[Wayne Mery (:wsmwk)]

Martin, any reason to believe this issue still exists?
If not, this can be closed - the reporter is no longer using Thunderbird.

Comment 5

[Martin Schröder [:mschroeder]]

(In reply to Wayne Mery (:wsmwk) from comment #4)

Martin, any reason to believe this issue still exists?
If not, this can be closed - the reporter is no longer using Thunderbird.

Wayne, I do not think it's worth leaving this issue open. I would expect a new bug report if there are still issues in this area,