3 ms·
>Instead of asking "Are you sure" to delete an element, just go ahead and delete it, but make it undoable. This allows for quicker workflow. Counterpoint: this
by Sir_Substance 8y ago
>Instead of asking "Are you sure" to delete an element, just go ahead and delete it, but make it undoable. This allows for quicker workflow.
Counterpoint: this makes it harder to tell that information that you might want to be really sure is deleted (like someone elses credit card number or your passport number) is actually deleted. The deletion workflow is now delete it->check to see if it's in the undo list->really for reals delete it.
That's a way worse UX than a confirm dialog, and more risky for the customer. Remember that your grandmother might be using this to temporarily store her credit card pin.
- dan-robertson 8y agoI don’t think clicking yes in a confirm dialog implies that anything was “truly deleted.” It might well still be living in the undo history, other indexes, auto save files, backups, and it could certainly live in memory (especially if it was moved by the garbage collector). It would be very foolish to assume that just because one has clicked “yes, delete” that the data is gone forever.