Created attachment 123455 [details] Unexpected selection in copy/move target. SUMMARY Dolphin (and also konqueror, if used as file browser) has changed its behavior for some time regarding the automatic selection of copied (or moved) files in the target. The old behavior (files added by copy action are marked after the copy process is finished) was (a) much clearer, as the arrival of the transferred files at the destination was clearly identifiable, (b) more practical, because you often process the transferred files in the target (open them for editing, change attributes, copy them again, or even move them back, ...) (c) consistent with the behavior of other common file managers (e.g. thunar, nautilus, Windows' explorer.exe, Mac Finder) and prior versions of konqueror (e.g. 4.13.3) and dolphin. STEPS TO REPRODUCE 1. Prepare some test directories and files: cd /tmp ; mkdir test1, mkdir test2; for i in $(seq 1 9) ; do touch /tmp/test1/$i ; done ; dolphin test1 2. F3 (split view) 3. Change to /tmp/test2 in the right panel (target) 4. Now select file 1 and 3 in the left panel ("source") and copy them to the "target" 5. Finally, select 2 and 4 in source and copy (or move) them to target (Step 3-5 see also enclosed video.) OBSERVED RESULT 1 and 3 stay selected in the target panel EXPECTED RESULT The new files (2 and 4) are selected in the target panel SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: 4.15.0-67-generic #76-Ubuntu SMP KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: Qt 5.13.1 (compiled against 5.13.1) ADDITIONAL INFORMATION Whether this is a bug or an intended feature is unclear. Indeed, you can argue about whether you want to equate adding files to a new multiple selection or not. But just that's why it's only logical to leave this choice to the user. Hence, the old behavior should be restored, just because the consistent user experience with other file managers as well as with earlier versions. Otherwise, if no longer standard, it should at least be a configurable option.
*** This bug has been marked as a duplicate of bug 402602 ***