123851 - cert picker doesn't default the OK button

Status: RESOLVED FIXED

(Core Graveyard :: Security: UI, defect, P3)

Description

[John G. Myers]

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

[John Unruh]

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.

Comment 2

[John G. Myers]

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).

Comment 3

[John G. Myers]

Enter key does nothing on Mac OS X.

Comment 4

[Stephane Saux]

changing platform to macsox.
I don't know why it would work on Windows but not on Mac.

Comment 5

[John G. Myers]

This is not MacOSX specific.  The button has the wrong (non-default) appearance
on Windows as well.

Comment 6

[Kai Engert (:KaiE:)]

Setting platform to all based on previous comment.

Comment 7

[John G. Myers]

Mass reassign ssaux bugs to nobody

Comment 8

[Nelson Bolyard (seldom reads bugmail)]

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.

Comment 9

[Stefan Borggraefe]

Fixed via bug 251991.