See bug 674088 for details:
Then, I looked at the "minor error" code, this is obviously not a minor error. I've noticed that changing mReadOnly and mDisabled does not actually change the properties "readOnly" and "disabled". I've fixed this by removing mDisabled and mReadOnly and just using the property getters directly.
Created attachment 8637361 [details] [diff] [review]
Fix - v1
r+ from the other bug
Backported to releases/comm-aurora changeset c53da8a616fa
Backported to releases/comm-beta changeset 18d4427d4203
Backported to releases/comm-esr38 changeset 59bfcc074820
Backported to releases/comm-aurora changeset 3638ae3dc946
Backported to releases/comm-beta changeset 3a6adf92dcac
Backported to releases/comm-esr38 changeset e08fb68b3474
This still needs to be checked in to cc - setting checkin-needed for this.
This patch is bitrotted for cc when applyied on top of the one from https://bugzilla.mozilla.org/show_bug.cgi?id=674088#c21
user: Philipp Kewisch <firstname.lastname@example.org>
date: Sat Aug 08 11:05:38 2015 +0100
Fix bug 1186547 - mReadOnly and mDisabled do not reflect readOnly and disabled properties. r=MakeMyDay
Is the 2nd checkin from comment 6/7/8 required for comm-central too?
Looking at http://mxr.mozilla.org/comm-central/source/calendar/providers/caldav/calDavCalendar.js#1888 this has already happened in the patch for bug 674088. There was a bit of a mess with the push messages here.
Could this be responsible for the regression reported in Bug 1195800 / Bug 1195974?
Yes, quite likely. I've set bug 1195974 to be tracked for 4.0.3
Patch was backed-out from Lightning 4.5, 4.4, 4.3 and 4.0 with Bug 1195974. Follow up in Bug 1201862.