Closed Bug 406895 Opened 18 years ago Closed 17 years ago

"Recently Bookmarked" smart folder is now added to "Bookmarks Menu" folder but only at end of folder contents

Categories

(Firefox :: Bookmarks & History, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: abillings, Unassigned)

Details

As of this last night's build, we seem to add a "Recently Bookmarked" smart folder to the "Bookmarks Menu" folder. (so far, so good...) I noticed that when this is automatically added to an existing profile, that it is tacked on to the *end* of the list of items in the "Bookmarks Menu" folder. This means, if you're looking for the folder in a sidebar, menu, or organizer, it is after everything. In my case, this meant it wasn't even immediately visible in any of my views because I have roughly 40 or so items under the "Bookmarks Menu" folder. When we create this, it should be added to the *top* of the folder, rather than to the end, in order to highlight it and make it visible in all views. Seen in Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b2pre) Gecko/2007120404 Minefield/3.0b2pre.
that code changed a lot, we are creating in the correct place now Mozilla/5.0 (Windows; U; Windows NT 6.0; it; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
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.