The default bug view has changed. See this FAQ.

sidebar and bookmarks library behave differently when adding separators

RESOLVED WORKSFORME

Status

()

Firefox
Bookmarks & History
RESOLVED WORKSFORME
9 years ago
4 years ago

People

(Reporter: juanb, Unassigned)

Tracking

3.0 Branch
PowerPC
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
Fx3rc1, 10.4.11, litmus test case 4121. Sidebar and bookmarks library behave differently when adding separators.

Sidebar, Steps:
1. Take for example the default Mozilla Firefox folder in the Bookmarks Menu.
2. Right-click on the Mozilla Firefox folder and select New Separator. 

Behavior, sidebar: A separator is added inside the Mozilla Firefox folder

Bookmarks Library, Steps:
1. Navigate to the Bookmarks Menu in the left pane
2. Right-click on the Mozilla Firefox folder and select New Separator

Behavior, library: A separator is added above the Mozilla Firefox folder

The behavior is inconsistent, and it can be a little frustrating if the user expects to be able to add a separator between two folders while in the sidebar, because they won't be able to. Unless they then drag the separator out of the folder, for example.

Comment 1

9 years ago
I agree.
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
they are now consistent afaict
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.