Closed Bug 536871 Opened 15 years ago Closed 14 years ago

Both "File Bookmark" and "Bookmark Manager" folders and subfolders appear to be empty after I have put bookmarks into them

Categories

(SeaMonkey :: Bookmarks & History, defect)

SeaMonkey 2.0 Branch
x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 597488

People

(Reporter: curiousjbh, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1

Both "File Bookmark" and "Bookmark Manager" subfolders appear to be empty after I have put bookmarks into them, either by clicking on them in "File Bookmark" or by "Drag'n'Dropping them into the "Bookmark Manager". The only place I can rely on seeing them is by invoking the actual bookmark menu system itself. So I use one of the two other methods to get a bookmark "approximately" where I want it, then I have to pull down the menu tree to get it positioned exactly where I want it. This is fraut with danger, a a false move could cause the bookmark to be *removed* from the menu tree.

Reproducible: Sometimes

Steps to Reproduce:
File a bookmark or manage bookmarks

Actual Results:  
Hit the "+" sign on a bookmark folder you've just put a bookmark in, and it changes to a "-" sign, but there's nothing in it.

Expected Results:  
Folder should change to a "-" sign, and the bookmark that I just put there shoud appear below it.

Running SeaMonkey Portable on 16GB Sandisk Cruzer Micro, originally 2.0, upgraded to 2.0.1.
It's not just subfolders - it's the main folders too.
Summary: Both "File Bookmark" and "Bookmark Manager" subfolders appear to be empty after I have put bookmarks into them → Both "File Bookmark" and "Bookmark Manager" folders and subfolders appear to be empty after I have put bookmarks into them
Version: unspecified → SeaMonkey 2.0 Branch
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.