373691 - deleting bookmarks from bookmarks manager with DEL key not possible anymore

Status: RESOLVED INCOMPLETE

(Firefox :: Bookmarks & History, defect)

Description

[Rotis]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2

Since FF 2.0.0.2 there is a new bug in the bookmarks manager. I select bookmarks I want to delete and press DEL (the "left arrow key" on the upper right on German Mac keyboards). Until 2.0.0.1 they got deleted immediately. In 2.0.0.2 they stay. When I close the bookmarks manager and reopen it they are gone. I don't know, if this problem always happens, but in my case it does since FF 2.0.0.2.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Roy K. Higashi]

Just wanted to add a couple of things:

This is similar to: Bug 373800 – Deleting multiple bookmarks under 2.0.0.2 does not reflect on display until clicked back to

This issue still exists in FF 2.0.0.3

When deleting multiple bookmarks in the bookmarks manager (especially after doing an large bookmark file import) the deletions are not reflected/updated/refreshed in neither the left or right pane of the bookmarks manager.  Both left and right panes of the bookmarks manager do reflect the deletions if I collapse and expand the "Bookmarks Folder" in the left pane ... HOWEVER ... when I close the Bookmarks Manager, the bookmarks listed in the left pane/sidebar of Firefox appear corrupted and show many blank empty folder entries after the "bottom" of the bookmarks list.  The only way to "fix" it is to close Firefox completely and then reopen Firefox.  After reopening Firefox the bookmarks list appears correctly.

Comment 2

[Shawn Wilsher :sdwilsh]

Bulk closing all UNCONFIRMED bugs dealing with places that haven't had any bug activity in over 120 days, have no votes, and are not enhancement requests.

If you are still experiencing this issue in Firefox 3.0 or later, please re-open the bug with steps to reproduce (if they were not part of the original comment).