Closed
Bug 335903
Opened 18 years ago
Closed 14 years ago
opening bookmarks manager displays name of profile LAST opened NOT CURRENTLY OPEN
Categories
(SeaMonkey :: Bookmarks & History, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mprober, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 This did not become apparent until after I installed four profiles in Mozilla email client and then proceded to organize the bookmarks for each of the profiles Each time I organized the bookmarks of a given profile and then reopened that profile they were NOT organized and in many instances the latest bookmarks added were nowhere to be found. After much frustration found the following: -Open profile "A" -Add new bookmark -open bookmark manager ( now shows name of profile LAST opened and bookmark is now installed in wrong profile "B", "C", "D",) Reproducible: Always Steps to Reproduce: 1.This error is consistent every time email started unless the profile last selected is opened again for the NEXT session. (this is how I was able to resolve this issue and finally get the bookmarks properly organized in all my profiles) 2. 3. Expected Results: It would certainly be helpful if when first opening 'BOOKMARKS' the selected profile name was displayed (and of course was the correct one)
Comment 1•16 years ago
|
||
MozillaAS v1.7.x is not supported anymore. Can you reproduce with SeaMonkey v1.1.9 ?
Version: unspecified → 1.7 Branch
I couldn't reproduce this bug with SeaMonkey 2.0b1pre/20090623, bookmarking (e.g. Bookmarks > Bookmark This Page/File Bookmark...) works as expected while switching between 3 different profiles. Related to/duplicate of bug 199404?
Comment 3•14 years ago
|
||
No answer to comment 1, marking INCO. Anyway, now with Places-based bookmarks, this is unlikely to be an issue anymore with SM 2.1pre.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•