Closed Bug 1190166 Opened 9 years ago Closed 8 years ago

When opening New Task dialog: 'Assert failed: aElement' thrown

Categories

(Calendar :: Tasks, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aryx, Assigned: MakeMyDay)

References

Details

Thunderbird 38.1.0, 40.0b1 and 42.0a1 20150801 on Windows 8.1

Clicking the New Task button in the toolbar opens the dialog but throws:

Timestamp: 02.08.2015 13:11:25
Error: Assert failed: aElement
2: [chrome://calendar/content/calendar-ui-utils.js:27] setElementValue
3: [chrome://calendar/content/calendar-ui-utils.js:81] setBooleanAttribute
4: [chrome://calendar/content/calendar-event-dialog.js:555] loadDialog
5: [chrome://calendar/content/calendar-event-dialog.js:297] onLoad
6: [chrome://calendar/content/calendar-event-dialog.xul:1] onload
7: [null:0] null

Source File: resource://calendar/modules/calUtils.jsm -> file:///C:/Mozilla/Debugging/Thunderbird/Profiles/unstable/central/Test-central-en/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calUtils.js
Line: 1001

This happens when button-freebusy gets hidden.
(In reply to Aryx [:archaeopteryx][:aryx] from comment #0)
> Thunderbird 38.1.0, 40.0b1 and 42.0a1 20150801 on Windows 8.1
Lightning 4.0.1.2, 4.2b1 and 4.4a1
I can see this on trunk, just clicking Write->Task.
This bug has been fixed with the patch for bug 1229148.
These code lines in the patch are reserved for this bug:
https://hg.mozilla.org/comm-central/rev/95367f284f9e#l2.12
they prevent the call to setElementValue with a null parameter (aElement="free-busy") when the free-busy button is hidden in the dialog.

makemyday, I set the assignment to you because you wrote a fix.
I think we can close this as fixed.
Assignee: nobody → makemyday
Status: NEW → ASSIGNED
Thanks. Yes, we can consider this to be fixed with bug 1229148 already.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → 4.7
Depends on: 1229148
You need to log in before you can comment on or make changes to this bug.