Closed
Bug 196705
Opened 23 years ago
Closed 16 years ago
Add Bookmark window probably should remember previous state
Categories
(SeaMonkey :: Bookmarks & History, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: danielbarclay.oss, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
The Add Bookmark window probably should remember its previous state (tree node
open/closed state, seletion, scroll position) when it is re-opened by the
File Bookmarks... command.
Consider the difference in the user's GUI gestures needed to filing several
related bookmarks:
For the first bookmark, the user clicks "File Bookmark...," the Add Bookmark
window opens, the user "navigates" to the appropriate bookmark folder, and
clicks "Okay" to file the bookmark and close the window.
Consider adding a second bookmark that goes in the same folder:
With the requested behavior, when the user opens the Add Bookmark window
again, the previous folder is selected. The user can simply click OK.
With the current behavior, the user has to repeat all his or her UI gestures
to get back to the same folder before clicking OK.
Also consider adding a bookmark that goes in a folder close to the first
folder:
With the requested behavior, the user has to "navigate" just a bit in the
folder tree to get to the target folder.
With the current behavior, the user has to repeat most of the navigation.
(Relatedly, note how Mozilla's use of a dialog box allows an improvement over
Netscape 4's use of a menu tree reflecting the bookmark folder tree.
Nested menus don't retain state from the previous use, so there is no way to
save the user from having to repeat all the navigation steps down the menu
hierarchy to the previous folder.
Since Mozilla uses a dialog box/window, and dialog boxes can retain state,
Mozilla can make filing a bookmark quicker by remembering the last-used folder,
saving the user many navigation steps.
(Remember that bookmarks lists can be large and deeply nested.)
)
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1•23 years ago
|
||
enhancement
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•21 years ago
|
||
I would love to see this bug addressed. The current behaviour of the "Add
Bookmark" dialog forces the user to repeat many actions.
This becomes frustrating when several bookmarks must be added to different folders.
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: bugs → nobody
QA Contact: chrispetersen → bookmarks
Comment 3•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
Comment 4•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•