Closed Bug 315908 Opened 20 years ago Closed 20 years ago

Cannot change Alarm values for a task.

Categories

(Calendar :: General, defect)

Sunbird 0.3a1
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cscj01, Assigned: jminta)

References

Details

Attachments

(1 file, 1 obsolete file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5 After creating a task and exiting the dialog, if you edit the task later, you cannot change the Alarm values. Reproducible: Always Steps to Reproduce: 1. Create new task; 2. set Alarm type, time, and when; 3. select OK; 4. edit task; 5. Alarm is grayed out. Actual Results: Could not change Alarm values. Expected Results: Alarm values not grayed out and capable of being changed.
What version of Sunbird/Calendar are you using? If you haven't tried testing this in 0.3a1 yet, please do so. 0.2 and the Calendar extension are rather out-dated.
Sorry. This is for 0.3a1.
Confirmed on Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051110 Mozilla Sunbird/0.3a1+. The following happens when I open the Edit Task dialog: Case 1: Start Date and Alarm were set: Alarm values are correctly displayed but all fields are disabled and can not be changed. Error in JSC: Error: startPicker is not defined Source File: chrome://calendar/content/eventDialog.js Line: 283 Case 2: Due Date and Alarm were set: Alarm type shows "Not specified" and can be changed. The remaining Alarm fields are disabled and can not be changed until Alarm type is set to popup or email. Case 3: Start Date, Due Date and Alarm were set: Same as in case 1. Nevertheless the alarm window shows pops up on the time set during task creation.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Sunbird 0.3a1
Attached patch use proper variable (obsolete) — Splinter Review
I think this fixes all of ssitter's cases. I also suspect that this is the underlying cause of bug 315874 and bug 231611 comment #6. Both those bugs should probably be closed if this is confirmed.
Assignee: mostafah → jminta
Status: NEW → ASSIGNED
Attachment #202678 - Flags: first-review?(mvl)
One extra change from the previous version to fix ssitter's case 2.
Attachment #202678 - Attachment is obsolete: true
Attachment #202689 - Flags: first-review?(mvl)
Attachment #202678 - Flags: first-review?(mvl)
Comment on attachment 202689 [details] [diff] [review] use proper variable and get correct element r=mvl
Attachment #202689 - Flags: first-review?(mvl) → first-review+
Blocks: 315874
Blocks: 231611
patch checked in
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: