Closed Bug 170721 Opened 23 years ago Closed 22 years ago

UTC event times are not converted into local times

Categories

(Calendar :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 188095

People

(Reporter: david.waring, Assigned: mostafah)

References

Details

I have subscribed to an ics file containing UTC times for events, these have not been converted into the local timezone (BST) for display in the calendar. ie DTSTART:20020925T183000Z should display as 25-Sep-2002 19:30:00 BST, however the event is being displayed at 18:30:00 on the calendar, this is incorrect.
->Mostafa
Assignee: mikep → mostafah
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
This cannot be properly fixed until we are able to span events over multiple days because an event in UTC may span over two days in local time So I'm adding dependancy on the bug that takes care of that issue.( Bug 133331 ).
Depends on: 133331
I am on a RedHat linux box. I find that if I close and re-open the Calendar window, events will then display as I expect. HOWEVER, after opening the Calendar window, opening the MailNews window now shows all dates in UTC. Re-launching Mozilla resets everything (MailNews displays dates properly until the Calendar is opened--Calendar must be opened twice to display events in local time).
I see this on OSX as well. I thought it was related to my Jaguar update but I guess not.
OS: Windows NT → All
Hardware: PC → All
duplicate of 188095 (which title is more explicit) ? "Z on the end of time stamp ignored. time zone misinterpreted" <http://bugzilla.mozilla.org/show_bug.cgi?id=188095>
Resolving as duplicate of bug 188095 which got fixed today. *** This bug has been marked as a duplicate of 188095 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!
QA Contact: colint → general
You need to log in before you can comment on or make changes to this bug.