Version: (using Devel) Installed from: Compiled sources In a folder with at least 2 element (file or folder), delete of them. No element is selected. I would expect that the next element ("next" to be consistent with the current sorting method) be selected. In case this was the last element, the previous element should be selected. By "Selected", I mean highlighted as I would have click on it.
*** This bug has been marked as a duplicate of bug 161675 ***
Peter, there is a difference (I'm referring to the bug 161675): he says that the previous file is selected after deletion. I can only see light dashed box around the previous file but if you press F2 for instance it won't allow you to rename the previous file. This is not what I call selected. For me, selected is ready for action on it and clearly highlighted (blue by default).
Ok, thanks for clarification, I've reopened this issue...
Resetting assignee to default as per bug #305719
*** Bug 320906 has been marked as a duplicate of this bug. ***
*** Bug 185188 has been marked as a duplicate of this bug. ***
*** Bug 400116 has been marked as a duplicate of this bug. ***
Done in current branch
On neon unstable, the next item is not selected after deleting by pressing delete key.
(In reply to Patrick Silva from comment #9) > On neon unstable, the next item is not selected after deleting by pressing > delete key. Should be in next 23.04 version
Git commit 36dfe5795f3e70ad9ac4954544899bf38c919ca7 by Serg Podtynnyi. Committed on 06/02/2023 at 03:47. Pushed by felixernst into branch 'master'. Selects next item in list after delete/trash actions Related: bug 419914 M +30 -0 src/views/dolphinview.cpp M +6 -0 src/views/dolphinview.h M +2 -0 src/views/dolphinviewactionhandler.cpp https://invent.kde.org/system/dolphin/commit/36dfe5795f3e70ad9ac4954544899bf38c919ca7