When adding a website to the exclusion list, ask the user what to do with already collected data
Bug #1442622 reported by
Steve Dodier-Lazaro
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| study.cs.ucl Password Collection Clients |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
Currently:
When the user adds a website to the exclusion list, she does not know what happens to already collected passwords for that website
Expected:
Propose the user to either erase already-collected entries, or keep them. Ideally, the erase option would take users through a list where they can select specific events they want to delete for the site (with Select All / Unselect All toggles)
| tags: | added: ethics |
| Changed in password-collection-wild: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| milestone: | none → rc1 |
| milestone: | rc1 → none |
| tags: | added: usability |
| Changed in password-collection-wild: | |
| milestone: | none → 1.0-ff |
To post a comment you must log in.
