Open Bug 1122762 Opened 9 years ago Updated 3 months ago

Give user an easy way to report filling issues

Categories

(Toolkit :: Password Manager, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: ckarlof, Unassigned)

References

Details

(Whiteboard: [passwords:telemetry] )

User Story

As a developer, I want to know which sites the password manager is providing a poor user experience so I can fix it.
Signals could include:

* user has a simple affordance to "report problem with password manager at site"
* user copies login credentials into a page that we already have saved
* user invokes a "fallback affordance" on page (bug 1122759)
:bsmedberg, what are the precedents for this, and what is the right tool? It's obviously a privacy concern, and IMO, this information (a domain) shouldn't be associated with broader user metrics. I hear content services is doing something similar, but running their own endpoint. Cloud Services can run an endpoint to collect this error reporting, too, if necessary.
Flags: needinfo?(benjamin)
Can we make this an opt-in UI? That would alleviate all of the concerns.

If that's not practical, let's talk; we can do this, carefully, and there are some new privacy tools for this that we'd like to try.
Flags: needinfo?(benjamin)
Priority: -- → P2
Whiteboard: telemetry
Component: Telemetry → Password Manager
Whiteboard: telemetry → [passwords:telemetry]
See Also: → 1213727

Moving to P3 as this is not happening in the next release cycle.

Priority: P2 → P3
Severity: normal → S3
Duplicate of this bug: 1213727

This is less about telemetry and more about giving user an easy way to let us know what and where failed to fill.

Summary: Collect domains where we get a strong signal that the password manager is failing the user → Give user an easy way to report filling issues
No longer blocks: password-telemetry
Severity: S3 → N/A
Type: defect → enhancement
You need to log in before you can comment on or make changes to this bug.