Closed Bug 422928 Opened 12 years ago Closed 12 years ago

Task mode, WCAP calendar: Cannot set completed Status

Categories

(Calendar :: Provider: WCAP, defect)

defect
Not set

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: berend.cornelius09, Assigned: dbo)

Details

Attachments

(1 file)

Steps to reproduce:
- go to task-mode and select a task of a WCAP calendar;
- open context menu and complete the task
- try to uncomplete the task

result:
the task does not get uncompleted. Instead only the "completed date" is set to "null" and thus removed from the tree. Uncompleting the task another time will finally also remove the "Completed" state.

I debugged into it and placed a breakpoint at "calendar-task-tree.xml" in the method "onModifyItem" where I could verify this behaviour: Setting the task (at the UI) to "incomplete" the first time will only change the "conpletedDate" property of "NewItem" and activating the transaction another time" will also change "IsCompleted" to false. 
The transaction is sent out in "calendar-task-tree.js", function "toggleCompleted"
Flags: blocking-calendar0.8?
As far as I tried out this behaviour could only be reproduced with WCAP-tasks.
Flags: blocking-calendar0.8? → blocking-calendar0.8+
Attached patch fixSplinter Review
Assignee: nobody → daniel.boelzle
Status: NEW → ASSIGNED
Attachment #309421 - Flags: review?(philipp)
Component: Calendar Views → Provider: WCAP
QA Contact: views → wcap-provider
Target Milestone: --- → 0.8
Comment on attachment 309421 [details] [diff] [review]
fix

r=philipp
Attachment #309421 - Flags: review?(philipp) → review+
Is there a relationship to Bug 415237?
Checked in on HEAD, MOZILLA_1_8_BRANCH and SUNBIRD_0_8_BRANCH => FIXED.

(In reply to comment #4)
Andreas mentioned the same and I had a look at that bug. No, this patch doesn't fix that, I'll comment on bug 415237.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
checked in nightly build 2008031704 (lightning) and 20080316 (sunbird)-> task
is fixed and verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.