Closed Bug 415253 Opened 16 years ago Closed 16 years ago

Reload causes error in hidden Unifinder [Error: unifinderTreeView.clearEvents is not a function]

Categories

(Calendar :: Calendar Frontend, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: ssitter, Assigned: ssitter)

References

Details

(Keywords: regression)

Attachments

(1 file)

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12pre) Gecko/2008020107 Calendar/0.8pre

Steps to Reproduce:
1. Start Sunbird with clean profile
2. Hide the unifinder using the Find Events toolbar button
3. Select menu File -> Reload Remote Calendars

Actual Results:
Error: unifinderTreeView.clearEvents is not a function
Source File: chrome://calendar/content/calendar-unifinder.js
Line: 118

Error: [Exception... "'[JavaScript Error: "unifinderTreeView.clearEvents is not a function" {file: "chrome://calendar/content/calendar-unifinder.js" line: 118}]' when calling method: [calIObserver::onLoad]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: file:///E:/sunbird/js/calUtils.js :: notifyFunc :: line 1560"  data: yes] STACK: 
1: [file:///E:/sunbird/js/calUtils.js:1563] notifyFunc
2: [null:0] null
3: [file:///E:/sunbird/js/calUtils.js:1566] calListenerBag_notify
4: [file:///E:/sunbird/components/calCompositeCalendar.js:364] anonymous
5: [null:0] null
Source File: file:///E:/sunbird/js/calUtils.js
Line: 1563
Attached patch fix, rev0Splinter Review
Assignee: nobody → ssitter
Status: NEW → ASSIGNED
Attachment #301550 - Flags: review?(philipp)
Flags: blocking-calendar0.8?
OS: Windows XP → All
Hardware: PC → All
Version: Trunk → unspecified
Attachment #301550 - Flags: review?(philipp) → review+
Checked in on HEAD and MOZILLA_1_8_BRANCH

-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Flags: blocking-calendar0.8?
Resolution: --- → FIXED
Target Milestone: --- → 0.8
checked in latest nightly build 20080207 -> task is fixed and verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.