I know there have been a TON of bugs complaining about seeing (EMPTY) for a newly created folder that actually has something in it. (And I know that empty goes away after you restart mozilla). What I noiced was that as I nest empty folders, and then expand then, sometimes the (empty) is NOT displayed. I know that is sounds silly to document that the problem that everyone else sees consistantly, I see go away every now and then. I just wanted to document this and maybe it will give someone a clue as to what is going on. On OpenVMS build 20020417, I created "New Folder##" (where ## = 1 thru 5) in bookmark manager and nested them under each other. When I expanded out my empty bookmark folders using the top level "Bookmark" menu item, I see the (empty) displayed for all of the folders. when I expand out the empty folders by clicking on the "personal toolbar" bookmark pop-up, one of the folders (New Folder3) does NOT list (empty). I went to a Lunix machine that I have access to, and with relase 2002041711, I was able to create the nested sub folders and when I expanded them out with BOTH the top level "Bookmarks" and the "Personal Toolbar" bookmark pop-up and each had different sub-folders missing (empty). I didn't see any ryme or reason for why some folders did not have (empty), and I tried different combinations of createing them with File|new|folder as well as the "new Folder" button in Bookmark manager. I also experimented to see if it made a difference if expandeding out the folders happened on the right or left of the display. (If your too far to the right, the expanded folder is shown on the left). Opened as trivial, since once the (empty) problem is fixed, I assume that this problem will be fixed as well.

Still a problem on Openvms build 20020513 (rc2)

I don't think, this is really a bug. It is probably a consequence of bug 79411, since you should not see (empty) in the first place. Is it OK to dupe this bug there? pi

*** Bug 146979 has been marked as a duplicate of this bug. ***

This is just more info about bug 79411 and shouldn't be a seperate bug, since fixing 79411 would automatically fix this one. Feel free to add your comments to that bug. *** This bug has been marked as a duplicate of 79411 ***

v