need watch cursor when restoring certs

NEW
Unassigned

Status

()

Core
Security: PSM
P5
enhancement
17 years ago
a year ago

People

(Reporter: bill, Unassigned)

Tracking

1.0 Branch
x86
Windows 2000
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [psm-smartcard])

(Reporter)

Description

17 years ago
There is no visual indication that the restore operation is actually working 
when restoring a certificate.  This is especially problematic when restoring a 
certificate/key to a smartcard (because they're slow devices).

What makes this confusing is that while the restore is apparently happening, you 
can move the mouse around and the cursor appropriately changes from a hand 
cursor to an arrow cursor as you mouse over hyperlinks within PSM.

Steps to reproduce:
install a smartcard on your machine
go into PSM and restore certificates to the smartcard
note that while the import operation is taking place, there is no watch cursor 
or any other indication that the machine is procesing.

If you wait long enough, you DO get the "restore was successful" dialog, but it 
takes long enough that the user might think the operation failed.

Comment 1

17 years ago
Changing to new.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

17 years ago
Changing QA contact to nitinp
QA Contact: junruh → nitinp

Comment 3

17 years ago
Mass reassigning nitinp's bugs to me.
QA Contact: nitinp → junruh

Comment 4

17 years ago
Future.
Target Milestone: --- → Future
Version: 1.2 → 2.0

Updated

16 years ago
Keywords: nsenterprise

Comment 5

16 years ago
removing nsenterprise keyword from PSM bugs with target milestone of future.
Keywords: nsenterprise

Comment 6

16 years ago
Mass assigning QA to ckritzer.
QA Contact: junruh → ckritzer

Updated

16 years ago
QA Contact: ckritzer → junruh

Comment 7

16 years ago
Enhancement
Assignee: ddrinan → ssaux
Severity: normal → enhancement

Updated

15 years ago
QA Contact: junruh → bmartin

Comment 8

14 years ago
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
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 → ---

Updated

13 years ago
Component: Security: UI → Security: UI
Product: PSM → Core
QA Contact: bmartin → ui

Updated

9 years ago
Version: psm2.0 → 1.0 Branch
Component: Security: UI → Security: PSM
Priority: P3 → P5
Whiteboard: [psm-smartcard]
You need to log in before you can comment on or make changes to this bug.