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}}).
* Alarms on recurring events often fail to fire, display, or be edited correctly; they should not be relied upon ({{bug|329985}}).


== Surprising Behavior ==
== Surprising Behavior ==
Line 13: Line 14:
* Outlook is unable to import some CSV-formatted calendar data exported from Lightning ({{bug|325484}}).
* 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}}).
* If one moves an event after dismissing the alarm for it, the alarm may not re-fire before the event as expected ({{bug|326352}}).
* Alarms on recurring events often fail to fire, display, or be edited correctly; they should not be relied upon ({{bug|329985}}).
* Lightning is not usable in the Japanese version of Windows 2000 ({{bug|330121}}).
* Lightning is not usable in the Japanese version of Windows 2000 ({{bug|330121}}).
* On Windows 98, if your profile path contains non-ASCII characters, Lightning will not work ({{bug 329898}}).


== Data Loss / Crashes Handling non-Lightning ICS Data ==
== Data Loss / Crashes Handling non-Lightning ICS Data ==
Confirmed users
2,615

edits

Navigation menu