Closed
Bug 82502
Opened 23 years ago
Closed 23 years ago
Space and Enter key treated differently in Composer
Categories
(Core :: DOM: Editor, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: doctor__j, Assigned: rubydoo123)
Details
Attachments
(1 file)
(deleted),
image/png
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9+) Gecko/20010523
BuildID: 2001052304
Reproducible: Always
Steps to Reproduce:
1. Open Composer
2. Type something
3. Close composer
4. When prompted for saving the file, press tab key to switch focus to "Don't
Save" and press Enter.
Actual Results: "Save" option is interpreted instead of "Don't Save" upon
hitting Enter.
Expected Results: Pressing Enter key on "Don't Save" button should be
equivalent to pressing Space Bar key on that button.
BTW, what's the difference between the thick black border around the "Save"
button and the thick grey border around the "Don't Save" button?
Any meaning? Or it's just another minor UI correctness problem?
Comment 2•23 years ago
|
||
So viewing a PNG triggers Quicktime plugin on 6.01, which doesn't display it
correctly! Could use GIFs, please?
But the differences you describe are important: the Enter key always triggers
the "Default" button, the one with the thick border. When you tab from button
to button, the thin border tells you what button is focused, and that is what
should be triggered with the Space bar. I.e., they are *not* the same.
That is proper Windows behavior.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Thanks Charles!
Wow! I learn a new thing on Moz keyboard nav...
But one more whining: It's not obvious enough... on my eyes at least... ;)
Comment 5•23 years ago
|
||
True, trying to come up with visual representations for "Default" vs.
"focused" is always a challenge in any OS. And customizing that in "themes"
makes it even harder for users to learn it!
You need to log in
before you can comment on or make changes to this bug.
Description
•