Closed Bug 396873 Opened 13 years ago Closed 13 years ago

Event dialog is messed up if being subscribed to old Sunbird calendar (Error "standard has no properties" in calUtils.js)

Categories

(Calendar :: Internal Components, defect)

defect
Not set

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: ssitter, Assigned: michael.buettner)

Details

Attachments

(1 file)

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.8pre) Gecko/20070919 Calendar/0.7pre

Event dialog is messed up if being subscribed to old Sunbird calendar (Error "standard has no properties" in calUtils.js)

1. Start Sunbird with clean profile
2. Subscribed to 
   http://dl.erweiterungen.de/kalenderdateien/Schulferien_2007-2008_SN.ics
3. Open New Event or New Task dialog

Actual results:
Dialog is messed up. All event and task controls are displayed at once.
Console shows:
    Error: standard has no properties
    Source File: chrome://calendar/content/calUtils.js
    Line: 168

From looking at the .ics file it seems that the calendar was created using Sunbird 0.2 or the old Calendar extension:

    BEGIN:VCALENDAR
    VERSION
     :2.0
    PRODID
     :-//Mozilla.org/NONSGML Mozilla Calendar V1.0//EN
    BEGIN:VTIMEZONE
    TZID
     :/Mozilla.org/BasicTimezones/GMT
    LOCATION
     :GMT
    END:VTIMEZONE
    ...
Attached patch patch v1Splinter Review
guessSystemTimezone() throws an exception in this case, which screws up the dialog at the end of the day.
Assignee: nobody → michael.buettner
Status: NEW → ASSIGNED
Attachment #281645 - Flags: review?(daniel.boelzle)
Comment on attachment 281645 [details] [diff] [review]
patch v1

r=dbo
Attachment #281645 - Flags: review?(daniel.boelzle) → review+
patch checked in on trunk and MOZILLA_1_8_BRANCH

-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: --- → 0.7
Verified using Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.8pre) Gecko/20071002 Sunbird/0.7
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.