Closed
Bug 268551
Opened 20 years ago
Closed 16 years ago
Folder appears in the bookmark menu and not on the toolbar after managing a folder
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: michali.sarris, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 If firefox is freshly started i can just add folder on the bookmark toolbar as i like (as supposed to). But if it then manage a folder in the bookmark menu, new folders added to the toolbar no longer appear on the toolbar it self, instead they appear to be created in the bookmark root. Reproducible: Always Steps to Reproduce: 1. Close firefox completely 2. Open a firefox browser window 3. Open the bookmarks menu 4. Manage a folder by rightclicking on it and choosing "Manage Folder" (for example: Firefox & Mozilla Information) 5. Close or do not close the manager (doesn't really matter) 6. Add a folder to the toolbar by rightclicking on it and choosing "New Folder...". Actual Results: A new folder was created in the bookmarks root. Expected Results: A new folder should have been created in the "Bookmark Toolbar Folder" instead.
Comment 1•20 years ago
|
||
I confirm (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0)
Comment 2•20 years ago
|
||
confirmed with Windows branch build 2004-11-07-07-0.11
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: vladimir → vladimir+bm
Assignee: vladimir+bm → nobody
Comment 3•18 years ago
|
||
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
Comment 4•16 years ago
|
||
actually invalid on current trunk Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a1pre) Gecko/20081215 Minefield/3.2a1pre
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•