Open
Bug 1201862
Opened 9 years ago
Updated 2 years ago
mReadOnly and mDisabled still do not reflect readOnly and disabled properties
Categories
(Calendar :: Provider: CalDAV, defect)
Calendar
Provider: CalDAV
Tracking
(Not tracked)
NEW
People
(Reporter: Fallen, Unassigned)
Details
There was quite a mess in bug 1186547, which caused bug 1195974. The issue that still exists is that mReadOnly and mDisabled are used. These should be replaced in a way that it retains the current behavior. Calendars that are not available shouldn't be disabled and made readonly, they should merely go into the error state and stay enabled. Calendars that are not DAV endpoints should be disabled.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•