https://bugs.kde.org/show_bug.cgi?id=474945
--- Comment #13 from orko <o...@igalia.com> --- I think there are potentially 2 issues here. 1. Whenever window dragging is started by the compositor, should it revert it to the original position? That directly seems to be the cause for the "jump" which is seen. It can be seen even when dragging another app, e.g. firefox, where a flicker is seen due to an initial jump when the dragging starts. See attached video: https://bugsfiles.kde.org/attachment.cgi?id=166734 2. The plasma wayland compositor starts the window drag and un-tiles immediately if an app sends `xdg_toplevel.move` in response to `wl_pointer.button`, as noted in https://issues.chromium.org/issues/40934397#comment14. As per https://wayland.app/protocols/xdg-shell#xdg_toplevel:request:move it seems that sending `xdg_toplevel.move` from the app "in response to some sort of user action like a button press" is a valid operation. Could the plasma wayland compositor delay the actual dragging and consequently un-tiling only after the mouse is moved ? -- You are receiving this mail because: You are watching all bug changes.
