summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKirill Chibisov <contact@kchibisov.com>2020-05-24 14:12:44 +0300
committerDaniel Stone <daniels@collabora.com>2020-06-12 21:15:11 +0000
commit57b7c7d9463f391a1cae6fa049b2f98a3de3d09e (patch)
treed1686415ec9eb6d414b3f5266b6cc4ec4e552342
parent4aa6eb868a8646b99c5b552a48aa31043530a269 (diff)
downloadwayland-57b7c7d9463f391a1cae6fa049b2f98a3de3d09e.tar.gz
Clarify clients behavior on wl_keyboard.leave
Clients must assume that every key, including modifiers, are lifted after getting wl_keyboard.leave event, not doing so could lead to key repeat keep going after the user changes focus, or stuck modifiers, when the user interacts with client without keyboard focus. Signed-off-by: Kirill Chibisov <contact@kchibisov.com>
-rw-r--r--protocol/wayland.xml3
1 files changed, 3 insertions, 0 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index 8e4a75c..9784680 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -2218,6 +2218,9 @@
The leave notification is sent before the enter notification
for the new focus.
+
+ After this event client must assume that all keys, including modifiers,
+ are lifted and also it must stop key repeating if there's some going on.
</description>
<arg name="serial" type="uint" summary="serial number of the leave event"/>
<arg name="surface" type="object" interface="wl_surface" summary="surface that lost keyboard focus"/>