Closed
Bug 150111
Opened 22 years ago
Closed 22 years ago
While trying to "Manage Bookmarks", cannot move bookmark into new folder
Categories
(SeaMonkey :: Bookmarks & History, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Alex, Assigned: bugs)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.0) Gecko/20020529 BuildID: 2002052918 Regarding bookmark management, specifically for your personal toolbar... it is easier to describe when listing the steps to reproduce, so please see below. However, in general... if you create a FOLDER on your personal toolbar, then go to manage bookmarks and attempt to move the first bookmarked item to the folder, you will be unsuccessful. All other bookmarks in your personal toolbar can be moved to the folder, with the exception of the first one. Reproducible: Always Steps to Reproduce: 1. Bookmark a site and place it on your personal toolbar 2. Go to manage bookmarks 3. Create a new folder on your personal toolbar 4. Try moving the FIRST item listed (the first item below 'Personal Toolbar Folder') to the new folder you just created. For me, it will not allow you to move that item. All other bookmarks in your personal folder can successfully be moved, however you cannot move the first item. Actual Results: Nothing... it simply will now allow you to move the first bookmarked item to the folder created.
Comment 1•22 years ago
|
||
Could you try with the latest trunk build, there have been some recent fixes concerning the issue you are reporting. If the issue still exists, please exactly report what are your bookmarks before DND, and tell us if your bookmarks were in sorted mode. Where are you dropping the bookmark in the personal folder? In the personal toolbar or in the bookmark manager?
Reporter | ||
Comment 2•22 years ago
|
||
Fixed in latest build.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•