Closed
Bug 23370
Opened 25 years ago
Closed 25 years ago
Migration: remember_selected_message true doesn't migrate right
Categories
(MailNews Core :: Profile Migration, defect, P3)
MailNews Core
Profile Migration
Tracking
(Not tracked)
VERIFIED
FIXED
M13
People
(Reporter: laurel, Assigned: sspitzer)
Details
Using jan06 builds on all platforms The pref for remember_selected_message doesn't show in 4.x prefs.js if the pref value is true (enabled). If a profile with this pref enabled in 4.x is migrated, the 5.0 UI will not pick up the pref enabled state (and doesn't show a pref line in the prefs.js file). Note: if the pref is enabled/checkmarked in 5.0, the enabled state will stick in UI and a line will be written to prefs.js with value set to true. 1. Open a profile in 4.x. 2. Edit|Prefs|Mail and Newsgroups. Enable/checkmark the preference "Remember the last selected message" and confirm OK. Exit 4.x. 3. Open 4.x prefs.js file and note there is no pref line for the relative pref: remember_selected_message. (If the 4.x pref is disabled/false there would be a prefs line.) 4. Migrate the profile to 5.0, go to mail. 5. Check the preference in the UI -- the pref is disabled/not checkmarked. 6. Check the 5.0 prefs.js file -- there is no prefs line. Actual result: The pref enabled in 4.x is not enabled in 5.0 after migration. User must set the pref to enabled state in 5.0. Expected result: The pref enabled in 4.x should migrate to enabled state in 5.0.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Target Milestone: M13
Assignee | ||
Comment 1•25 years ago
|
||
fixed. the problem was we never defined a default for this pref in mailnews.js
Now the UI is correctly enabled after migration. There is still no pref.js line written for the case of enabled/true. OK using: 2000-01-18-11m13 commercial build on NT 4.0 2000-01-18-11m13 commercial build on linux 6.0
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•