Closed Bug 1622693 Opened 4 years ago Closed 3 months ago

Record in telemetry when a login save/update happens on a site the user has a breached login for

Categories

(Toolkit :: Password Manager, task, P3)

Product:
Toolkit
Component:
Password Manager
Type:
task

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: MattN, Unassigned)

References

Details

(Whiteboard: [passwords:capture-UI] [passwords:telemetry])

Right now we only know if a user changes their breached password from within about:logins but it's more common for the password to be changed and the user uses the save/update doorhanger instead. To understand how many people are taking the correct action and changing their password, it would be good to measure the save and update in this case. The save is useful (above the update) to handle if the username doesn't match the one saved either because it was wrong in storage or when captured. We should probably count save and update separately though.

See Also: → 1631130
Severity: normal → S3
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.