Closed
Bug 123851
Opened 23 years ago
Closed 20 years ago
cert picker doesn't default the OK button
Categories
(Core Graveyard :: Security: UI, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jgmyers, Unassigned)
Details
Mozilla 0.9.8
Client Certificate Selection set to "Ask Every Time"
User certificate and key installed
Connect to https site that requests client authentication using the CA that
issued the user certificate.
Expected result: Cert picker appears with the user certificate selected and the
[OK] button showing with default-button appearance. Pressing the return key
dismisses the dialog, selecting the cert.
What happens: The [OK] button has normal, non-default appearance. Pressing the
return key has no effect.
This is a regression from 0.9.5 and 0.9.6 (in 0.9.6, the button didn't appear,
but pressing the return key usually worked correctly).
Comment 1•23 years ago
|
||
I cannot reproduce with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:0.9.8+) Gecko/20020206 or the trunk build - Mozilla/5.0 (Windows; U; Windows
NT 5.0; en-US; rv:0.9.8+) Gecko/20020206 Netscape6/6.2.1+
The OK button is not highlighted, but pressing enter selects the cert shown and
proceeds the user past the dialog.
Reporter | ||
Comment 2•23 years ago
|
||
Ok, the enter key works for me on Windows (but the OK button is not
highlighted). I'll retest on Mac OS X tonight or tomorrow (that machine is at
home).
Reporter | ||
Comment 3•23 years ago
|
||
Enter key does nothing on Mac OS X.
Comment 4•23 years ago
|
||
changing platform to macsox.
I don't know why it would work on Windows but not on Mac.
OS: All → MacOS X
Priority: -- → P3
Hardware: All → Macintosh
Target Milestone: --- → Future
Reporter | ||
Comment 5•23 years ago
|
||
This is not MacOSX specific. The button has the wrong (non-default) appearance
on Windows as well.
Comment 6•22 years ago
|
||
Setting platform to all based on previous comment.
OS: MacOS X → All
Hardware: Macintosh → All
Comment 8•21 years ago
|
||
Mass change "Future" target milestone to "--" on bugs that now are assigned to
nobody. Those targets reflected the prioritization of past PSM management.
Many of these should be marked invalid or wontfix, I think.
Target Milestone: Future → ---
Comment 9•20 years ago
|
||
Fixed via bug 251991.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•