Closed
Bug 261481
Opened 21 years ago
Closed 21 years ago
Sorting should not be automatic. Sorting should be on demand.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 211023
People
(Reporter: rich, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.9.3 StumbleUpon/1.995
Build Identifier: Mozilla Firefox 1.0PR Preview Release
Bookmarks within Folders on the Bookmarks Sidebar are automatically sorted
Bookmarks within Folders on the Bookmarks Toolbar cannot be sorted.
This is both great and terrible. It is great because if Bookmark Toolbar
folders were automatically sorted, any bookmark dragged into a folder would
disappear and be impossible to find if that folder was filled already with many
hundreds of bookmarks. Finding that bookmark again is like looking for a needle
in a haystack because the names on new bookmarks are often not the names we
expect.
On the other hand, it is terrible that Bookmarks within Folders on the Bookmarks
Toolbar are never sorted because a bookmark containing 900 unsorted bookmarks is
not of much use.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Expected Results:
What is needed is for Firefox sorting to be only on demand, never automatic, and
for sorting to apply only to one folder and its subfolders not all folders.
This way the folders on the Bookmarks Toolbar could be sorted. Once a folder
and its subfolders are sorted, they should remain sorted. "Unsorted" should be
removed from the Sort menu. The Unsorted command is crazy. Who really wants to
unsort their folders and have everything scrambled? What we really want is to
turn off the auto-sort function. And be able to sort each folder on demand
after we've had the opportunity to read new bookmark names and give them better
names.
Comment 1•21 years ago
|
||
Choose "Unsorted" to turn off "automatic sorting" in the sidebar, upgrade to
Firefox 1.0PR, and use the new "Sort By Name" feature in the context menu for
bookmark folders.
*** This bug has been marked as a duplicate of 211023 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•