Closed
Bug 413128
Opened 16 years ago
Closed 16 years ago
All calendars are deselected after Lightning update
Categories
(Calendar :: General, defect)
Calendar
General
Tracking
(Not tracked)
VERIFIED
FIXED
0.8
People
(Reporter: sebo.moz, Assigned: dbo)
Details
(Keywords: regression)
Attachments
(1 file)
1.78 KB,
patch
|
Fallen
:
review+
|
Details | Diff | Splinter Review |
After Lightning update all calendars are deselected. This happens when updating from a build prior to 20080106 with a build starting from Lightning 2008011604. The same error has caused a lot of confusion when releasing 0.7. Requesting blocking status.
Flags: blocking-calendar0.8?
Updated•16 years ago
|
Flags: blocking-calendar0.8? → blocking-calendar0.8+
Comment 1•16 years ago
|
||
Works for me after updating from Sunbird/Lightning 0.7 to current 0.8pre builds.
Reporter | ||
Comment 2•16 years ago
|
||
I cannot reproduce as well if I start from Lightning 0.7. I can still reproduce with clean profile if switching from Lightning 20080105 to Lightning 20080116.
Comment 3•16 years ago
|
||
I can reproduce if upgrading from an older 0.8pre to a current 0.8pre. However, because the error doesn't occur when upgrading from 0.7 it's not a blocker. But it should stay on the table for retest once the final 0.8 builds are available.
Reporter | ||
Comment 4•16 years ago
|
||
Note to self/QA: Upgrade path from 0.5 to 0.8 should also be tested.
Comment 5•16 years ago
|
||
I did testing for 0.5 --> 0.8pre, which failed ;-(
Comment 6•16 years ago
|
||
As ssitter noted in the other bug I can't remember right now, testing 0.5 -> 0.8 will obviously fail since 0.5 -> 0.7 failed. Its the same issue. As long as 0.7 -> 0.8 is fine, I think we are good to go. I'd still be interested whats causing this though.
Assignee | ||
Comment 7•16 years ago
|
||
I can imagine a rather easy fix checking for either "calendar-main-in-composite" or "lightning-main-in-composite" in calProviderBase; taking this one.
Assignee: nobody → daniel.boelzle
Assignee | ||
Comment 8•16 years ago
|
||
Attachment #301735 -
Flags: review?(philipp)
Assignee | ||
Updated•16 years ago
|
Status: NEW → ASSIGNED
OS: Windows XP → All
Hardware: PC → All
Target Milestone: --- → 0.8
Comment 9•16 years ago
|
||
Comment on attachment 301735 [details] [diff] [review] fix r=philipp
Attachment #301735 -
Flags: review?(philipp) → review+
Assignee | ||
Comment 10•16 years ago
|
||
Checked in on HEAD and MOZILLA_1_8_BRANCH => FIXED.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 11•16 years ago
|
||
Comment on attachment 301735 [details] [diff] [review] fix + function takeOverIfNotPresent(oldPref, newPref, dontDeleteOldPref) { ... + takeOverIfNotPresent("lightning-main-in-composite", "calendar-main-in-composite"); + takeOverIfNotPresent("lightning-main-default", "calendar-main-default"); Can someone explain this mysterious third parameter to me? None of the callers use it...
Assignee | ||
Comment 12•16 years ago
|
||
It's a pleasure to do this: I actually recycled this function from another patch that will soon land (presumably post 0.8), i.e. for bug 412800. That patch will set up more composite calendars for today pane et al and take over the current composite props without deleting them.
Comment 13•16 years ago
|
||
(In reply to comment #10) > Checked in on HEAD and MOZILLA_1_8_BRANCH => FIXED. Verified FIXED with Lightning 2008020719 doing an update from 0.5 release.
You need to log in
before you can comment on or make changes to this bug.
Description
•