https://bugs.kde.org/show_bug.cgi?id=509231
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Version| |6.21 Fixed/Implemented| | In| | Status|ASSIGNED |RESOLVED Latest Commit| |https://invent.kde.org/fram | |eworks/kio/-/commit/8e6cfd3 | |b6a7e55777208d3c5755ffefcb5 | |6d4098 --- Comment #3 from Nate Graham <[email protected]> --- Git commit 8e6cfd3b6a7e55777208d3c5755ffefcb56d4098 by Nate Graham, on behalf of Rafał Lichwała. Committed on 10/12/2025 at 05:44. Pushed by ngraham into branch 'master'. kfileplacesview: remove DropAction::MoveAction from the list of supportedActions When we drag some item from "Places View" and drop it to some other destination folder, there is `DropAction::MoveAction` allowed (on the drop popup menu) which makes the source item is physically moved to destination folder and it is removed from the source (but not from "Places View", so user even does not know the item has been removed). This commit corrects this behavior in two aspects: 1. It removes `DropAction::MoveAction` from the list of `supportedActions` in `KFilePlacesView::startDrag` method 2. It prevents putting plugin custom actions to drop popup menu as they can have also Move-like destructive consequences Now, when we drag some item from "Places View" to any other folder we just have "Copy" and "Link" default actions in drop popup menu. Even when "Move by default" setting is set, such drop popup menu is always displayed (and does not contain Move-like actions). FIXED-IN: 6.21 M +3 -1 autotests/dropjobtest.cpp M +8 -1 src/filewidgets/kfileplacesview.cpp M +12 -1 src/widgets/dropjob.cpp https://invent.kde.org/frameworks/kio/-/commit/8e6cfd3b6a7e55777208d3c5755ffefcb56d4098 -- You are receiving this mail because: You are watching all bug changes.
