Closed Bug 974816 Opened 12 years ago Closed 12 years ago

right click in the calendar list bring up wrong calendar property dialog after toggle offline

Categories

(Calendar :: Dialogs, defect)

Lightning 2.6.4
x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: weichen302, Assigned: weichen302)

References

Details

Attachments

(1 file, 1 obsolete file)

Reproducible: Always Steps to Reproduce: Right click on a network calendar, in the properties dialog, toggle offline mode, accept change, then right click the same calendar again, open the properties dialog, this time the dialog shows properties of the calendar below, unless it right clicked calendar is the last one. patch: right click a calendar in calendar tree will assign it to compositeCalendar.defaultCalendar, if right click that calendar again without click another calendar, the compositeCalendar.defaultCalendar is unchanged. It is normally okay until toggle calendar offline status from the right click => properties dialog, the offline toggling remove old one, assign next calendar to compositeCalendar.defaultCalendar, and does not assign the newly created cached/uncached calendar to compositeCalendar.defaultCalendar after done. The next time right click on calendar will bring up the properties dialog of the calendar below it, unless it is the last one in the tree view.
Attachment #8378866 - Flags: review?(philipp)
Assignee: nobody → weichen302
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment on attachment 8378866 [details] [diff] [review] fix right click bring up wrong calendar property dialog Looks good, r=philipp
Attachment #8378866 - Flags: review?(philipp) → review+
Comment on attachment 8378866 [details] [diff] [review] fix right click bring up wrong calendar property dialog Review of attachment 8378866 [details] [diff] [review]: ----------------------------------------------------------------- ::: calendar/base/content/widgets/calendar-list-tree.xml @@ +499,5 @@ > + composite.defaultCalendar.id != > + this.getCalendar(this.tree.currentIndex).id) { > + composite.defaultCalendar = this.getCalendar( > + this.tree.currentIndex); > + } Actually, these lines could be split up a bit with local variables, and it looks like there are some minor whitespace issues. I'll fix this before checkin.
Attached patch Fix - v2Splinter Review
Here is the patch for checkin
Attachment #8378866 - Attachment is obsolete: true
Attachment #8392456 - Flags: review+
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → 3.1
Target Milestone: 3.1 → 3.3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: