Closed Bug 113280 Opened 23 years ago Closed 10 years ago

OCSP Response Signers drop-down too narrow

Categories

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

Product:
Core Graveyard
Component:
Security: UI
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: junruh, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [kerh-coz]) 

1.) Edit>Prefs>Privacy>Validation
2.) Select a Response Signer.
What happens: The list is too narrow to be able to read any of the full names.
Priority: -- → P3
Target Milestone: --- → 2.2
*** Bug 116522 has been marked as a duplicate of this bug. ***
nsbeta1
Keywords: nsbeta1
Keywords: nsbeta1 → nsbeta1-
Blocks: 157555
Keywords: nsbeta1
Keywords: nsbeta1-
OS: Windows 2000 → All
Hardware: PC → All
Target Milestone: 2.2 → 2.4
Version: 2.2 → 2.4
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
Product: PSM → Core
Whiteboard: [kerh-coz]
changing obsolete psm* target to --- (unspecified)
Target Milestone: psm2.4 → ---
QA Contact: junruh → ui
Version: psm2.4 → 1.0 Branch
among them, the following have this problem:
Builtin Object Token:AOL Time Warner Root Certification Authority 1
Builtin Object Token:AOL Time Warner Root Certification Authority 2

Builtin Object Token:Verisign Class 1 Public Primary Certification Authority
Builtin Object Token:Verisign Class 1 Public Primary Certification Authority - G2
Builtin Object Token:Verisign Class 1 Public Primary Certification Authority - G3

I suppose a tooltip could work....
Version: 1.0 Branch → Trunk
As of bug 531067, we don't even have default OCSP responders. I believe the relevant UI was taken out some time before that, as well.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.