Closed
Bug 1078094
Opened 10 years ago
Closed 7 years ago
iCal export specifies times with wrong timezone data
Categories
(Mozilla Reps Graveyard :: reps.mozilla.org, task, P2)
Mozilla Reps Graveyard
reps.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Unfocused, Assigned: mkohler)
References
Details
(Whiteboard: has-pr)
The iCal export of events seems to specify times incorrectly - it specifies a timezone reference, but then uses a UTC time.
For instance, in one event that is set to happen at 5.30pm in New Zealand, the iCal has the following:
DTSTART;TZID=Pacific/Auckland:20141007T043000
DTEND;TZID=Pacific/Auckland:20141007T060000
If DTSTART/DTEND include a timezone reference, the time needs to be local to that timezone. However, it's being given as UTC time. So in the above example, it's saying the event starts at 4.30am local time.
Fix is to either correctly give local time, or to just remove the timezone reference and specify UTC (add a trailing "Z").
Relevant iCal spec reference: http://www.kanzaki.com/docs/ical/dateTime.html
And the above example is from: https://reps.mozilla.org/e/codecraft-dunedin-october-meetup/
Assignee | ||
Updated•7 years ago
|
Priority: -- → P2
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → me
Assignee | ||
Comment 3•7 years ago
|
||
PR opened here: https://github.com/mozilla/remo/pull/1416
Status: NEW → ASSIGNED
Whiteboard: has-pr
Comment 4•7 years ago
|
||
Commits pushed to master at https://github.com/mozilla/remo
https://github.com/mozilla/remo/commit/3f4a92df7df63e0137bf7be0e74af5dbacd9437c
Bug 1078094 - Always use UTC in iCal for events
https://github.com/mozilla/remo/commit/0459dae0acfe0967860df21cad4552954eb0a534
Merge pull request #1416 from MichaelKohler/feature/bug1078094_ical_fix
Bug 1078094 - Always use UTC in iCal for events
Assignee | ||
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•