Commit 53dd9979 authored by Nick Yamane's avatar Nick Yamane Committed by Simon Ser
Browse files

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 Yamane's avatarNick Diego Yamane <nickdiego@igalia.com>
parent 1ab6a818
Pipeline #220262 passed with stages
in 1 minute and 21 seconds
......@@ -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
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment