Closed Bug 106652 Opened 23 years ago Closed 22 years ago

[RFE] on File Bookmark, would like focus on last 'Create In' Folder not 'Name'

Categories

(SeaMonkey :: Bookmarks & History, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 75452

People

(Reporter: mozbugz, Assigned: bugs)

Details

see summary.. its a pain to choose the folder again, and again.. for adding
bookmarks say for many bugzilla bug-id URL's.  I hardly ever change the 'Name'
area.. where focus is now; and I would like the focus to be on the last folder I
added a bookmark to instead.  would cut down on my clicking/mouse moving.. and
having to tab down for the keyboard people.  that way the focus could be in the
'Create in' Dialog area, and then I can quickly traverse the tree for the folder
with the Up/Down arrow keys if I dont want to use the last 'create in' folder
for the last filed bookmark.
Most users use the keyboard to enter a title and the mouse to select a folder.  
I don't think this would be a good idea.
I agree with Jesse that given the frequency with which `File Bookmark' will be 
used just to give the bookmark a sensible name, focus should be on the name 
field by default. (Similarly, the native save file dialogs on both Windows and 
Mac OS give initial focus to the `Name' field, not the folder list.)

However, I do think the last-used folder (and scroll position in the folder 
list) should be remembered. Currently it isn't, and fixing that would make 
people need to use the `Create in:' field much less often.
OS: Windows 2000 → All
Hardware: PC → All
Severity: normal → enhancement
mpt, bug 75452

Dennis, what do you think of these comments ? Are you happy with
having this bug marked as a duplicate of bug 75452 ?
No complaint in a month.

pi

*** This bug has been marked as a duplicate of 75452 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Agreed with Jesse. Marking VERFIED DUP (or WONTFIX).
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.