Closed
Bug 986984
Opened 12 years ago
Closed 11 years ago
Timezone / Time changes when event is moved to another calendar
Categories
(Calendar :: Provider: GData, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bugexpend, Unassigned)
Details
Attachments
(1 file)
|
736 bytes,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Firefox/17.0 (Nightly/Aurora)
Build ID: 20121119183901
Steps to reproduce:
Received event in email as .ics attachment.Clicked on "This message contains and event - Add to calendar"
Event correctly added to "Local" Calendar.
Edited event - changed from Local to synced Google Calendar in drop down menu.
Saved event.
Actual results:
New edited event now shows up 12 hours ahead in UST.
I'm in New Zealand UST -12hours.
Expected results:
Expected time of event to have stayed the same, just the Calendar it was showing in to have changed.
If I use copy and paste, from Local to GoogleCal, this works as expected.
Updated•12 years ago
|
Attachment #8395475 -
Attachment mime type: text/calendar → text/plain
Comment 1•12 years ago
|
||
If you enable the "Show Timezone" option in the event dialog, what timezone shows up once you've changed the calendar?
Also, could you enable calendar.debug.log and calendar.debug.log.verbose in the advanced config editor? The event you attached is in floating timezone (local), it may be that the Provider for Google Calendar doesn't support floating timezones.
Component: Lightning Only → Provider: GData
(In reply to Philipp Kewisch [:Fallen] from comment #1)
> If you enable the "Show Timezone" option in the event dialog, what timezone
> shows up once you've changed the calendar?
Original Event "Local Time"
Changed Calendar "Pacific/Auckland" and leaps forward 12 hours
>
> Also, could you enable calendar.debug.log and calendar.debug.log.verbose in
> the advanced config editor? The event you attached is in floating timezone
> (local), it may be that the Provider for Google Calendar doesn't support
> floating timezones.
Enabled them now.
Comment 3•11 years ago
|
||
There has been a major rewrite of the Provider for Google Calendar between version 0.32 and 1.0. A vast number of bugs have been fixed during this rewrite, therefore I am closing lots of old bugs that I think might either be fixed or no longer apply to the latest version.
Please read the updated FAQ [1] for details on known issues. If you can reproduce your issue with the latest version of the Provider for Google Calendar and you can't find an existing bug that handles your case, please reopen this issue.
Thank you for your understanding.
[1] https://wiki.mozilla.org/Calendar:GDATA_Provider
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•