[dolphin] [Bug 492404] Dolphin doesn't select the parent folder when Up or Back is being pressed
flan_suse
bugzilla_noreply at kde.org
Thu Feb 27 21:36:07 GMT 2025
https://bugs.kde.org/show_bug.cgi?id=492404
flan_suse <windows2linux at zoho.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |windows2linux at zoho.com
--- Comment #28 from flan_suse <windows2linux at zoho.com> ---
Ben, I appreciate your feedback and tests, which show how this problem affects
more than one thing about the user experience.
Unfortunately, I think that trying to go point by point misses the bigger
picture: Deselecting an opened item or visited folder should never have been
made into the default, and I would argue it should never have made it into KDE
*at all*. The reasons are plenty. You've explained some yourself. So have I in
another bug report. So has another user on Reddit.
The best solution is to revert this change that breaks workflow and muscle
memory. I have yet to see a large userbase request that Dolphin diverge from
all other file browsers in this regard. (To the devs: Make an "option" in
Dolphin f it's really that important. You can call it "Deselect opened files
and folders".)
No other OS'es or DE's do this: Not Windows, COSMIC, MATE, Xfce, GNOME, or even
earlier versions of KDE.
If the rationale is "We want to prevent users from accidentally deleting their
files", then it still doesn't make sense in the context of KDE:
1. This is babysitting users, without a means to disable the "safety feature"
2. It's *inconsistent* with KDE: They recently added a new context menu called
"Extract here and delete", which cannot be removed from the menu. I have
accidentally trashed my archives multiple times because of this menu item. I
cannot even disable it. This is sending mixed messages: "We want to protect our
users from accidentally deleting things, but also we want to make it really
easy to accidentally delete things".
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list