Calendar:Lightning:0.1:Known Issues: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 5: Line 5:
* Lightning behaves unreliably with dates before 1970 or after 2037; failure modes may include JavaScript exceptions and crashes ({{bug|278236}}).  Workaround: don't enter such dates.
* Lightning behaves unreliably with dates before 1970 or after 2037; failure modes may include JavaScript exceptions and crashes ({{bug|278236}}).  Workaround: don't enter such dates.
* Multiple users or computers editing the same calendar can collide and cause data loss ({{bug|329570}}).
* Multiple users or computers editing the same calendar can collide and cause data loss ({{bug|329570}}).
== Surprising Behavior ==
* Delete a local calendar.  Create a new one.  The old events show up in the new calendar ({{bug|296202}}).  Workaround: create the new calendar before deleting the old one.
* Some failures when creating or viewing a calendar for the first time do not display an error dialog, though information is available in the JavaScript console ({{bug|328618}}).
* Default timezone guessing is unreliable, especially in the southern hemisphere ({{bug|328996}}).  Note that all events that you edit or create will end up in the default timezone.  Workaround: manually set your timezone in the Lightning panel of the Options or Preferences dialog.
* Setting your timezone manually does not completely take effect until Thunderbird has been restarted ({{bug|329669}}).
* Outlook is unable to import some CSV-formatted calendar data exported from Lightning ({{bug|325484}}).
* If one moves an event after dismissing the alarm for it, the alarm may not re-fire before the event as expected ({{bug|326352}}).


== Data Loss Handling non-Lightning ICS Data ==
== Data Loss Handling non-Lightning ICS Data ==
Line 16: Line 24:
* X- components are stripped out when editing or importing a calendar that contains them ({{bug|322837}}).
* X- components are stripped out when editing or importing a calendar that contains them ({{bug|322837}}).
* X- parameters are stripped out when editing or importing a calendar that contains them ({{bug|322831}}).
* X- parameters are stripped out when editing or importing a calendar that contains them ({{bug|322831}}).
== Surprising Behavior ==
* Delete a local calendar.  Create a new one.  The old events show up in the new calendar ({{bug|296202}}).  Workaround: create the new calendar before deleting the old one.
* Some failures when creating or viewing a calendar for the first time do not display an error dialog, though information is available in the JavaScript console ({{bug|328618}}).
* Default timezone guessing is unreliable, especially in the southern hemisphere ({{bug|328996}}).  Note that all events that you edit or create will end up in the default timezone.  Workaround: manually set your timezone in the Lightning panel of the Options or Preferences dialog.
* Setting your timezone manually does not completely take effect until Thunderbird has been restarted ({{bug|329669}}).
* Outlook is unable to import some CSV-formatted calendar data exported from Lightning ({{bug|325484}}).
* If one moves an event after dismissing the alarm for it, the alarm may not re-fire before the event as expected ({{bug|326352}}).


== CalDAV Bugs ==
== CalDAV Bugs ==
Confirmed users
2,615

edits

Navigation menu