Closed
Bug 244519
Opened 20 years ago
Closed 13 years ago
Remove confusion over 'sort' options in Bookmark Manager
Categories
(SeaMonkey :: Bookmarks & History, defect)
SeaMonkey
Bookmarks & History
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dc2, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a1) Gecko/20040520 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a1) Gecko/20040520 The Bookmark Manager in 1.8a has been changed so clicking the tree column heading just changes the presentation of the tree as elsewhere in Mozilla (not sorts the bookmark data as before), which is fine as it stops users accidently ruining their bookmarks by misunderstanding the kind of sort being used. However the options in the edit menu are still called 'sort' which still leaves room for doubt. A synonym like 're-order' would be better instead. Another problem is the CTRL+N shortcut for 'Sort Folder by Name' which sorts without any confirmation. Elsewhere in Mozilla, CTRL+N opens a new browser window. Maybe it would be better to remove this shortcut? If the changes sound okay, I can work on this patch if nobody else has the time. See also http://www.mozillazine.org/talkback.html?article=4774#2 (Bookmark sorting). Reproducible: Always Steps to Reproduce:
Comment 1•20 years ago
|
||
Neil, what do you think? What wording do you suggest? Dan, if we decide to change it, I'd like to change it everywhere, not only in the UI (e.g. there's a method sortFolder).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•20 years ago
|
Product: Browser → Seamonkey
(In reply to comment #0) > Another problem is the CTRL+N shortcut for 'Sort Folder by Name' which sorts > without any confirmation. This seems to be bug 209355.
Comment 4•13 years ago
|
||
Bookmarks Manager has been rewritten to use the Places Backend. Obsoleting this bug. Please file a new bug for issues with the new Bookmarks Manager.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•