Closed
Bug 359116
Opened 19 years ago
Closed 15 years ago
Theme preference not retained after software update from 1507->1508
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: marcia, Unassigned)
Details
Seen while testing software update on the Mac. I have now seen this on both the PPC Mac and the Intel Mac, with slightly different variations.
STR (seen on PPC)
1. Run the 1508 candidate build and change your theme. Restart Tbird to confirm the theme has been installed and is visible in the UI
2. In order to test updates, go back to 1507 using the same profile. Confirm that the theme you had set is visible when you launch 1507.
3. Adjust the channel pref to test software update. Apply the update and restart.
Result: The theme you had previously set as default is not visible in the UI. If you go into Theme Manager the theme you picked seemingly shows as the default (the Use Theme button is greyed out), but the Tbird default theme shows in the UI. The only way to get back the theme is to set Tbird default theme back to the default, restart, and then apply your theme all over again.
On the Intel Mac, all I had to do was set my theme in 1508 and go back to 1507, and the theme was gone, with the same results as above - the Thunderbird default theme shows in the UI but in Theme Mgr the theme I had selected seems to still be the default.
I tried a brief test of this on Firefox, and did not see this behavior.
Comment 1•19 years ago
|
||
I was not able to recreate this problem on my Intelmac. The theme I had set to default remained as default when I went from 1.5.0.8 -> 1.5.0.7 -> update to 1.5.0.8. I have no extensions other than Talkback and no Themes other than the default (plus the added Tiger Mail 2.1.1).
Comment 2•19 years ago
|
||
Now I see that if I try a complete update (forced) from 1.5.0.7 to 1.5.0.8, the Theme selection will not be kept.
Reporter | ||
Comment 3•19 years ago
|
||
The scenario I am most concerned about is when users go from 1507->1508 and lose their theme preference. Juan was not able to reproduce that scenario. It seems so far that this only happens when going back and forth.
Reporter | ||
Comment 4•19 years ago
|
||
ok, I have new results while testing on a PPC mac (10.3.9)
1. Created a new profile in a fresh install of 1507. I then added the Mostly Crystal theme and the Enigmail extension.
2. Changed the update channel to "releasetest" and checked for updates. Update was found, and I applied it.
3. Upon restart, the Mostly Crystal theme was no longer the default, and the Thunderbird Theme shows in the UI, yet the Mostly Crystal "Use Theme" button is greyed out.
Changing summary to reflect this new behavior. Next steps is to see if this can be reproduced on other platforms besides PPC Mac.
Summary: Theme preference not retained when going backwards (1508->1507) → Theme preference not retained after software update from 1507->1508
Reporter | ||
Comment 5•19 years ago
|
||
Please see my results at http://wiki.mozilla.org/Firefox:1.5.0.8:Test_Plan:Software_Update#marcia to see instances where this occurs. So far the only consistent has been en-US 1507->1508
Comment 6•19 years ago
|
||
WFM on Windows XP x64. I did the strs from the wiki and from juans comment #2. Themes that i had installed (Mostly Crystal and phoenity) were applied after software update / forced update.
Comment 7•19 years ago
|
||
This worked for me on my Mac, but I've seen it happen on Marcia's. I'm using a PPC mac running 10.4.8. After upgrading to 1.5.0.8, the mostly crystal theme was still used as the default.
Reporter | ||
Comment 8•19 years ago
|
||
Definitely still seeing this using version 2 beta 1 (20061115), but it could be profile related.
Comment 9•17 years ago
|
||
(In reply to comment #8)
> Definitely still seeing this using version 2 beta 1 (20061115), but it could be
> profile related.
Marcia, going from 1.5.x to 2.x?
Assignee: mscott → nobody
Comment 10•15 years ago
|
||
not confirmed on v3, so not keeping.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•