Closed Bug 405949 Opened 17 years ago Closed 17 years ago

rearranging bookmark in folder by drag'n'drop puts it in a random location in folder

Categories

(Firefox :: Bookmarks & History, defect, P3)

x86
macOS
defect

Tracking

()

RESOLVED DUPLICATE of bug 405087

People

(Reporter: Dolske, Unassigned)

Details

I have folders on my bookmark toolbar. If I drag'n'drop one of the items already in the folder to a different position in the menu, it seems to end up in a random location in the menu (or sometimes doesn't move at all).

1) Click once on folder to open dropdown menu
2) Click-and-drag a bookmark to a location a few entries up or down in the menu
3) Release mouse button

The bookmark that was dragged should end up where you dropped it. I've seen it jump to the end, only move 1 spot, move half-way, or not move at all. I'm not sure what the pattern is, it seems random.

This is especially annoying because sometimes when opening a folder I'll fumble a bit and accidently drag the first bookmark a couple of pixels. If I'm lucky it won't move, if I'm unlucky it jumps to somewhere else in the folder.

Rearranging the bookmarks in the Bookmarks Organizer works fine.

Maybe a widget bug?
Flags: blocking-firefox3?
Status: NEW → RESOLVED
Closed: 17 years ago
Flags: blocking-firefox3? → blocking-firefox3+
Priority: -- → P3
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.