Closed
Bug 549395
Opened 15 years ago
Closed 13 years ago
Add relnote for 'browser.toolbars.showbutton.* = false' setting is not migrated
Categories
(SeaMonkey :: Website, defect)
SeaMonkey
Website
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sgautherie, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: relnote)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.23) Gecko/20090825 SeaMonkey/1.1.18] (release)
1. Create a new 1.1 profile.
2. Set |user_pref("browser.toolbars.showbutton.home", false);|
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.8) Gecko/20100205 SeaMonkey/2.0.3] (release)
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.9pre) Gecko/20100301 SeaMonkey/2.0.4pre] (nightly)
3. Create a new 2.0 profile.
4. Migrate from 1.1 profile: |seamonkey -P <NameOf20Profile> -migration|.
4r. 'Home' button is displayed.
***
From bug 531526, I understand we don't want to migrate the pref itself.
But we should convert the setting (= customize the toolbar) nonetheless.
If that's not possible, we could probably just warn in the release note:
http://www.seamonkey-project.org/releases/seamonkey2.0.3/
NB: I didn't check '....bookmarks' and '....print' yet.
![]() |
||
Comment 1•15 years ago
|
||
> But we should convert the setting (= customize the toolbar) nonetheless.
I don't think that this is possible inside the migrator as the new settings are persisted in localstore.rdf.
> If that's not possible, we could probably just warn in the release note:
> http://www.seamonkey-project.org/releases/seamonkey2.0.3/
Yes a relnote seems appropriate.
Keywords: relnote
![]() |
||
Comment 2•15 years ago
|
||
(In reply to comment #1)
> Yes a relnote seems appropriate.
Can you write up one, I guess you mean under "Known Issues"? I also guess it should mention all browser and mailnews buttons that had should prefs?
Apart from that, this bug is WONTFIX, right?
Reporter | ||
Updated•15 years ago
|
Flags: wanted-seamonkey2.1?
Flags: wanted-seamonkey2.0?
![]() |
||
Comment 3•15 years ago
|
||
The wanted-seamonkey2.0 flag doesn't have any practical value any more, as the 2.0 series has already shipped and is stable.
Flags: wanted-seamonkey2.0?
Comment 4•15 years ago
|
||
modifying summary to go with agreed solution.
Component: Startup & Profiles → Project Organization
QA Contact: profile-manager → organization
Summary: 'browser.toolbars.showbutton.home = false' setting is not migrated → Add relnote for 'browser.toolbars.showbutton.* = false' setting is not migrated
![]() |
||
Comment 5•15 years ago
|
||
OK, I'll wait until someone provides a good relnote and tells me in what chapter of the relnotes to put it, then I'll do that.
Reporter | ||
Comment 6•15 years ago
|
||
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.3a4pre) Gecko/20100328 SeaMonkey/2.1a1pre] (nightly)
Same with trunk.
Version: SeaMonkey 2.0 Branch → Trunk
![]() |
||
Comment 7•15 years ago
|
||
> Same with trunk.
Yes but the relnote is for the 2.0 release branch.
OS: Windows 2000 → All
Hardware: x86 → All
Version: Trunk → SeaMonkey 2.0 Branch
![]() |
||
Comment 8•15 years ago
|
||
(In reply to comment #7)
> Yes but the relnote is for the 2.0 release branch.
If someone writes it up, at least.
If a relnote surfaces here until tomorrow, it can even be part of the 2.0.4 relnotes when it ships *hint* but I have too little clue and time to write it up myself.
![]() |
||
Updated•15 years ago
|
Component: Project Organization → www.seamonkey-project.org
Flags: wanted-seamonkey2.1?
Product: SeaMonkey → Websites
QA Contact: organization → www.seamonkey-project-org
Version: SeaMonkey 2.0 Branch → unspecified
Comment 9•13 years ago
|
||
2.0 is long gone and I don't see much sense in adding this to current relnotes (I feel the Known Issues section is listing too many edge cases already). Reopen if you feel necessary, but if you do, please provide an explanation.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Websites → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•