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

[Tom]

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

            Bug ID: 424723
           Summary: UX improvement to avoid data-loss when pressing 'back'
                    or 'up'.
           Product: dolphin
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: panels: folders
          Assignee: dolphin-bugs-null at kde.org
          Reporter: tomz at freedommail.ch
                CC: kfm-devel at kde.org
  Target Milestone: ---

Dolphin has a hard rule on what do to if you enter a folder from one of its
subfolders. It selects the folder you 'came' from. This has UX problems, though
as this is a bit random and allows people to lose their data.

STEPS TO REPRODUCE
1. Start dolphin, for instance from krunner typing 'Downloads'.
2. Press 'up'.
3. Notice that 'Downloads' is selected
4. An unsuspecting user might not notice and select a file in this dir by the
'plus' hover icon.
5. pressing 'delete' now moves to trash 2 items, while the user never selected
the dir.


It seems that Dolphin by default always selects the one folder it came from,
overruling any selection that was there before.

To work towards a solution I would like to invite you to try one more test:

1. open dolphin and select any directory
2. navigate 'up'.
3. press outside of all items in order to remove the selection.

Notice that at this point your folder you came from still has an underline. A
simple 'return' will enter that dir again.

I would like to suggest that instead of selecting an item that Dolphin only
sets the anchor. Or does an m_selectionManager->clearSelection(); after the
current select.

This gives all users the benefits they currently have and this avoids the
problem of unsuspecting users losing directories by deleting them because
Dolphin auto selected the folder for them.

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