diff options
| author | Nick Diego Yamane <nickdiego@igalia.com> | 2020-07-08 10:48:19 -0400 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2020-10-29 12:17:28 +0000 |
| commit | 53dd99793dd95fcfc187a0ee81ab289dfbe7fc2a (patch) | |
| tree | 67e37c6c758b1ff8ae6c2ef1821dce25f0378ca5 | |
| parent | Fix undefined behavior (diff) | |
| download | wayland-53dd99793dd95fcfc187a0ee81ab289dfbe7fc2a.tar wayland-53dd99793dd95fcfc187a0ee81ab289dfbe7fc2a.tar.gz wayland-53dd99793dd95fcfc187a0ee81ab289dfbe7fc2a.tar.bz2 wayland-53dd99793dd95fcfc187a0ee81ab289dfbe7fc2a.tar.lz wayland-53dd99793dd95fcfc187a0ee81ab289dfbe7fc2a.tar.xz wayland-53dd99793dd95fcfc187a0ee81ab289dfbe7fc2a.tar.zst wayland-53dd99793dd95fcfc187a0ee81ab289dfbe7fc2a.zip | |
protocol: Clarify how clients can cancel a drag operation
Explicitly say that destroying a wl_data_source previously used in a
wl_data_device::start_drag request will cancel the DND session. This
is currently the only way to do it from client side (besides those
"indirect" ones already documented) and all compositors work like that
but it is not clear spec-wise it is the expected behaviour.
Signed-off-by: Nick Diego Yamane <nickdiego@igalia.com>
| -rw-r--r-- | protocol/wayland.xml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 09e4f4c..3475a79 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -829,7 +829,8 @@ for the eventual data transfer. If source is NULL, enter, leave and motion events are sent only to the client that initiated the drag and the client is expected to handle the data passing - internally. + internally. If source is destroyed, the drag-and-drop session will be + cancelled. The origin surface is the surface where the drag originates and the client must have an active implicit grab that matches the |