Closed
Bug 130913
Opened 23 years ago
Closed 23 years ago
[mac] Keyboard navigation in Dialogs needs to be off
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 132720
People
(Reporter: mhaecker, Assigned: bugzilla)
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.9) Gecko/20020311
BuildID: 2002031106
When a dialog is opened I frequently try to accept it with <return> or to cancel
it with <command-.>. The second one works pretty well, but when I try to accept
it with return I often falsely do something else, because some other controll
currently has keyboard focus and therefore receaves the activate event. :(((((
As far as I know this is deffinitely silly! The default button is called the
default button, because it acts as one and gets pressed if <return> is pressed. :-(
Reproducible: Always
Steps to Reproduce:
1.Do something that opens a Dialog with more than one buttons. The security
manager asking to save a password is a great example.
2. With this Dialog open, look which buttton gets called when you hit return, or
move the focus around with the tab key. :(
3.
Actual Results: Whatever Buttton has focus gets called.
Expected Results: Whenever I hit return the Default Buttton has to be
activated. No matter what has focus.
By the way: Whats this keyboard navigation thing in Dialogs anyway????
;-) Just kidding, but as far as I know the HIG this should be turned of by
default and left for the powerusers that do use it.
Comment 1•23 years ago
|
||
This was fixed in bug 132720, "Return and Enter keys do not correctly confirm
OK/Cancel dialogs [Mac only]".
If you don't like keyboard navigation in dialogs, don't press the tab key :) If
you find any dialogs where a non-default button is focused when you first open
the dialog, please file a new bug.
*** This bug has been marked as a duplicate of 132720 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•