Validation prefs tab needs cleanup



Core Graveyard
Security: UI
17 years ago
2 years ago


(Reporter: Bob Lord, Assigned: David P. Drinan)


1.0 Branch

Firefox Tracking Flags

(Not tracked)


(Whiteboard: PDT+; critical for 0.9.2)


(1 attachment)



17 years ago
The OCSP section of the Validation pref tab needs a number of changes.

(1) The URL and the Signer areas should be reversed. (This relates to #2 to
improve flow.)
(2) When you select a Signer whose cert contains the AIA extension, the system
should auto-populate that extension into the URL field.
(3) The list of Signers should be sorted so that the certs with the AIA
extension are filtered to the top (and then sorted alphabetically). There should
be a horizontal rule between the top list (which contains certs with AIA
extensions) and the bottom list (without the extensions). A sample list would be:

Abc corp
RTFM corp
XYZ corp
AAA Corp
Bbbb Inc.

(4) The URL text area is locked.  I can't enter in any text there.
(5) Some Signer names are too long, so the button extends off the edge of the
window.  Perhaps we should clip the names at 20 (25? 30?) characters.

Regarding #3, this organization may not be the best to easily convey the meaning
between the certs.  It will not be intuitive why company X has certs both above
and below the line.  Smart users will figure it out, but it will take some

Another option would be to leave the list sorted as, but to put the certs with
AIA extensions in bold, or to someone tag them as being special.

Comment 1

17 years ago
-> 2.0

Priority: -- → P1
Target Milestone: --- → 2.0

Comment 2

17 years ago
I'd be happy if we just fixed items #1 and #5.

Comment 3

17 years ago
bug 81529 seems to cover issue #5

Comment 4

17 years ago
Whiteboard: PDT

Comment 5

17 years ago
PDT+ as per Steve Elmeer 6/20/2001
Whiteboard: PDT → PDT+


17 years ago
Whiteboard: PDT+ → PDT+; eta 6/22

Comment 6

17 years ago
Created attachment 39564 [details] [diff] [review]
Patch. Javi, please review.

Comment 7

17 years ago

Comment 8

17 years ago

Please super-review.

Whiteboard: PDT+; eta 6/22 → PDT+; need sr=, need a=

Comment 9

17 years ago
Ready for sr=, a=

Comment 10

17 years ago
David, that patch only seems to cover change #1.  Were you going to propose a
patch to cover change #5 later?

Comment 11

17 years ago
Does #5 mean the button is not visible or is not clickable?  If either is the
case, then that would be critical to fix.  If the button is clickable but looks
a little goofy then we've got enough to be worth getting in today (UI
localization freeze is 6/26.)

Who is the sr= person for this bug?
I was the sr person for this bug but I told the person who requested the
super-review to respond to bob's comments first.

Comment 13

17 years ago
Note regarding #5: while the button is "at rest" it should be truncated to fit
in the window.  But when you click on it and the popup list is exposed, you
should see the entire name of the CA.  

If that's not a simple change, then we should just complete #1 (which I think we
have), and I'll open a new bug for the other remaining points to prevent too
much bug morphing.
In that case Bob let me know if you want me to super-review just #1 then.

Comment 15

17 years ago

What you propose for #5 is not simple to do. So, as you suggest, the best is to 
check in #1 and open a new bug for the remaining deficiencies. 


Please just super-review #1.

Comment 16

17 years ago
whiteboard -> needs review.
Whiteboard: PDT+; need sr=, need a= → PDT+; needs review;

Comment 17

17 years ago
Chris, I think the consensus on this is to have you sr #1.
sr=blizzard, a=blizzard on behalf of drivers for 0.9.2
Whiteboard: PDT+; needs review; → PDT+; critical for 0.9.2

Comment 19

17 years ago
Fixed on branch and trunk.
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 20

17 years ago
Verified #1 was fixed.


14 years ago
Component: Security: UI → Security: UI
Product: PSM → Core


10 years ago
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.