After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 712348 - Prevent accidential password deletion with one click
Prevent accidential password deletion with one click
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
: 706486 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-11-15 05:15 UTC by Kalle Richter
Modified: 2018-04-16 22:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kalle Richter 2013-11-15 05:15:57 UTC
It shouldn't be possible to delete (possibly important, but also all other) passwords with one click. Improvement alternatives:
1.) Add undo button to password text field 
2.) Change function of close button to discarding changes and add a save button taking over the function of close button
Deleting passwords with one click is possible when selecting the text of password and pressing insert instead of copy or cut accidently.
Comment 1 Christian Haug 2016-02-07 19:27:50 UTC
Very nice suggestion, this is desperately needed! I just lost the results of 6 hours worth of video editing. A cancel or undo button would surely have been a blessing in this situation.
Comment 2 ThrowMeOut 2017-11-22 11:43:02 UTC
This just happened to me for the N-th time, and really ticked me off. I even registered this account (which is a throw-away; please remove it) just to report this. It turned out, I'm not an exceptional case.

The occurrences when I flimsily hit CTRL and turn my password into a 'c' have been a case. Then there is the inexplicable case of where I just end up with an empty field. Sometimes, my thumb extends a bit too much, and ALT+TAB'ing leaves me with a blank as my stored secret.

I cannot stress this enough, but this needs improvement. Have the field read-only and add a big EDIT button, or a confirmation after it has changed, to at least stop the user, or anything really from freestyle editing a secret after it has been stored.

I hope this gets noticed and evaluated as important. This is causing a lot of grief for me today.

Thank you.
Comment 3 Niels De Graef 2018-03-10 19:33:27 UTC
This is fixed on master as of commit a0a5f533.
Comment 4 Andy 2018-04-16 22:00:55 UTC
*** Bug 706486 has been marked as a duplicate of this bug. ***