Closed Bug 242716 Opened 22 years ago Closed 22 years ago

"Bookmarks Toolbar" unavailable after selecting "Restore default set" in "View > Toolbars > Customize..."

Categories

(Firefox :: Toolbars and Customization, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED DUPLICATE of bug 221482

People

(Reporter: petrovicky, Assigned: bugs)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040505 Firefox/0.8.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a) Gecko/20040505 Firefox/0.8.0+ When you want to change the toolbars a bit with "View > Toolbars > Customize..." and decide to "Restore default set", FireFox correctly restores the default set, but also restores the default Bookmarks Toolbar view. When you go to "Bookmarks > Bookmarks Toolbar Folder", you still see the bookmarks that were there before you pressed "Restore default set". But, anyway, there's no way to get them back to the "Bookmarks Toolbar" until you restart the browser (hiding and showing the toolbar again does not help). When you restart the browser, the Bookmarks Toolbar is back again with all its items. Reproducible: Always Steps to Reproduce: 1. Put some bookmarks into the "Bookmarks Toolbar Folder" 2. Set the "Bookmars toolbar" to be visible. 3. Use the "Restore default set" in "View > Toolbars > Customize..." Actual Results: The "Bookmarks Toolbar" has been replaced by the one that's used with a clean install of Firefox. Expected Results: The "Bookmarks Toolbar" should show the items that "Bookmarks Toolbar Folder" contains.
I can reproduce this as well. On windows XP using Firefox 0.9 RC
I can see this on Win2000 using firefox 0.9 RC Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040608 Firefox/0.8.0+
Looks like this is a duplicate of Bug 221482
Marking as dupe of bug 221482. *** This bug has been marked as a duplicate of 221482 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
QA Contact: bugzilla → toolbars
You need to log in before you can comment on or make changes to this bug.