diff options
| author | David Edmundson <davidedmundson@kde.org> | 2024-09-26 12:15:37 +0100 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2025-05-20 20:20:13 +0000 |
| commit | 3214f858e2bc226c16c280d832a836eae8a671c4 (patch) | |
| tree | 7f7f38dad903a92de0191f766ab2ea82f58f6d48 | |
| parent | shm: linkify function references in docs (diff) | |
| download | wayland-3214f858e2bc226c16c280d832a836eae8a671c4.tar wayland-3214f858e2bc226c16c280d832a836eae8a671c4.tar.gz wayland-3214f858e2bc226c16c280d832a836eae8a671c4.tar.bz2 wayland-3214f858e2bc226c16c280d832a836eae8a671c4.tar.lz wayland-3214f858e2bc226c16c280d832a836eae8a671c4.tar.xz wayland-3214f858e2bc226c16c280d832a836eae8a671c4.tar.zst wayland-3214f858e2bc226c16c280d832a836eae8a671c4.zip | |
protocol: Clarify sending of wl_seat.capabilities
It wasn't explicitly stated that wl_seat.capabilities should also
be sent on bind. Everyone did because it was obviously sensible.
This also clarifies that static seat name should be sent before
announcing capabilities so clients can associate these devices with the
right seat name.
Signed-off-by: David Edmundson <davidedmundson@kde.org>
| -rw-r--r-- | protocol/wayland.xml | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 1af51d3..a87d07f 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -1913,9 +1913,10 @@ <event name="capabilities"> <description summary="seat capabilities changed"> - This is emitted whenever a seat gains or loses the pointer, - keyboard or touch capabilities. The argument is a capability - enum containing the complete set of capabilities this seat has. + This is sent on binding to the seat global or whenever a seat gains + or loses the pointer, keyboard or touch capabilities. + The argument is a capability enum containing the complete set of + capabilities this seat has. When the pointer capability is added, a client may create a wl_pointer object using the wl_seat.get_pointer request. This object @@ -1997,9 +1998,9 @@ The same seat names are used for all clients. Thus, the name can be shared across processes to refer to a specific wl_seat global. - The name event is sent after binding to the seat global. This event is - only sent once per seat object, and the name does not change over the - lifetime of the wl_seat global. + The name event is sent after binding to the seat global, and should be sent + before announcing capabilities. This event only sent once per seat object, + and the name does not change over the lifetime of the wl_seat global. Compositors may re-use the same seat name if the wl_seat global is destroyed and re-created later. |