Closed Bug 417594 Opened 16 years ago Closed 16 years ago

Deleting a separator in personal toolbar folder deletes bookmark

Categories

(Firefox :: Bookmarks & History, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 403263

People

(Reporter: sicking, Unassigned)

Details

(Keywords: dataloss)

Steps to reproduce:

1. Create a folder on the personal toolbar and insert a few bookmarks and
   separators
2. Open folder in the personal toolbar
3. Rightclick a separator
4. Choose delete

Actual result:
Bookmark immediately above separator is deleted

Expected result:
Separator should be deleted

This is extra bad since there seems to be no way to recover the lost bookmark. This has happened to me a number of times lately since various bookmark synchronizations has resulted in many duplicated separators. Attempting to delete these separators results in the bookmark being lost.
Flags: blocking-firefox3?
Bug 403263? should be a blocker however, we don't want dataloss
Component: Bookmarks → Places
QA Contact: bookmarks → places
Definitely blocking, but this might just be the effect of one of many targetting bugs in bookmark drop-down menus, or a dupe of bug 403263 as Marco suggests.
Flags: blocking-firefox3? → blocking-firefox3+
Ideed looks like a dupe
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h".

In Thunderbird 3.0b, you do that as follows:
Tools | Message Filters
Make sure the correct account is selected. Click "New"
Conditions: Body   contains   places-to-b-and-h
Change the action to "Delete Message".
Select "Manually Run" from the dropdown at the top.
Click OK.

Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter.

Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in before you can comment on or make changes to this bug.