Calendar:Sunbird:0.3a2:Known Issues

General Data Loss

• On Windows, events sometimes show up at the wrong times if you have "Automatically adjust clock for daylight saving changes" unchecked in the Timezone tab of the Date and Time control panel (bug 326868). Workaround: check the "Automatically adjust clock for daylight saving changes" box.
• Setting Sunbird's timezone to something different then the system timezone will result in errors in the displayed times
• Shutting down Sunbird does not wait for pending calendar writes to complete, which could cause calendar corruption. Workaround: wait 5 seconds after the last calendar modification before exiting Thunderbird (bug 328810).
• Sunbird 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).
• Alarms on recurring events often fail to fire, display, or be edited correctly; they should not be relied upon (bug 329985).

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 Sunbird Options or Preferences dialog.
• Outlook is unable to import some CSV-formatted calendar data exported from Sunbird (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).
• [rv:1.8_branch] Sunbird 0.3a2 will not work if the date format starts with year and the date separator is set to the slash '/' character (e.g., Windows 2000 locales: Japan, South Africa). Workaround: set the separator to the hyphen (minus) character (e.g., in Windows 2000 use Control Panel/Regional Options/Date). (bug 330121. bug 307895 is fixed for rv:1.9).
• It is not possible to cancel the 'All Occurrences'/'This Occurrence' dialog. Pressing escape or clicking on the window close box acts as though 'This Occurrence' was selected (bug 329642).

Data Loss / Crashes Handling non-Sunbird ICS Data

Sunbird is not really ready to be used to modify ICS data that it did not itself generate. If you decide that you want to do this anyway, here are some things to be aware of:

• VALARM support is not yet complete (bug 308538). Importing or modifying calendars that contain VALARMs created by other programs will either fail or strip out any non-understood data.
• VTIMEZONE data produced by programs other than Sunbird will be generally be read and understood, and should in theory be preserved, but this is not well tested (bug 314339).
• VEVENTs with a DURATION but no DTEND are converted to DTSTART+DTEND-style events upon importing or editing a calendar that contains them (bug 317786).
• Inline attachments and attachment parameters will either cause errors or be stripped out when importing or editing a calendar that contains them (bug 319909).
• 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- properties and X- components can trigger crashes (bug 314334).

CalDAV Bugs

CalDAV has not been a focus for version 0.3a2; CalDAV support is currently very basic and has many issues. In addition to the various problems described in the non-Sunbird ICS section above, other things to be aware of include:

• Editing recurring items may fail or lose data (bug 327990, bug 328576). No workaround known.
• Sunbird may inadvertantly strip out server-side item changes that happen after a PUT.