Confirmed users
2,615
edits
Calendar:Lightning:0.1:Known Issues: Difference between revisions
Jump to navigation
Jump to search
→Surprising Behavior
| Line 22: | Line 22: | ||
* 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}}). | * 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. | * 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. | ||
* Outlook is unable to import some CSV-formatted calendar data exported from Lightning ({{bug|325484}}). | |||
== CalDAV bugs == | == CalDAV bugs == | ||
* There is no UI to specify a username and password for a CalDAV account ({{bug|308567}}). Workaround: specify both the username and password in the calendar URI. Note that this workaround is a poor idea from a security standpoint. Be sure to URL-encode appropriate characters (e.g. the @ symbol). | * There is no UI to specify a username and password for a CalDAV account ({{bug|308567}}). Workaround: specify both the username and password in the calendar URI. Note that this workaround is a poor idea from a security standpoint. Be sure to URL-encode appropriate characters (e.g. the @ symbol). | ||
* Editing recurring items may fail or lose data ({{bug|327990}}, {{bug|328576}}). No workaround known. | * Editing recurring items may fail or lose data ({{bug|327990}}, {{bug|328576}}). No workaround known. | ||