[dolphin] [Bug 424723] UX improvement to avoid data-loss when pressing 'back' or 'up'.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=424723

Nate Graham <nate at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nate at kde.org

--- Comment #4 from Nate Graham <nate at kde.org> ---
Every action is undoable, and all potentially destructive actions show a
confirmation dialog. Even moving items to the trash shows a confirmation
dialog.

Now, yes, the user may not notice what they have selected. They may not read
the dialogs. They may not know how to undo. They may bypass the trash and
delete directly for whatever reason.

But eventually you have to treat the user as an adult and expect that they take
responsibility for their actions in an environment where there are already
reasonable safeguards. This is especially true for users who use the dangerous
"delete immediately" action. If you use that, you ought to know what you're
doing and be paying attention. There's a reason why it's not the default
deletion action and why the trash paradigm exists. If you deliberately bypass
the safeguards and do something potentially dangerous, it's on you to make sure
that you don't blow anything up.

If we add more safeguards, people will start to complain that the warnings slow
them down. If we remove the "select previous folder when going back" behavior,
people will complain about that, because it will interfere with their ability
to use keyboard navigation.

The one thing I think we could do here is to make undo more obvious by
displaying a little tiny (emphasis on tiny) time-limited notification inside
the UI with an undo button in it after move, copy, deletion (etc.) actions. A
lot of mobile apps do this to increase the discoverability of their undo
actions for deletion in particular, and I think it's a good UI innovation.

Do you think that would help?

-- 
You are receiving this mail because:
You are on the CC list for the bug.