diff options
| author | Bhushan Shah <bshah@kde.org> | 2020-10-07 14:40:37 +0530 |
|---|---|---|
| committer | Bhushan Shah <bhush94@gmail.com> | 2020-11-03 20:16:27 +0530 |
| commit | 4ed0cafeefd9f81b974465ca495cbd9118508cdb (patch) | |
| tree | 3c3e4db17651f4a54aaf29acd280b859ea10b586 /unstable/linux-explicit-synchronization | |
| parent | 3a74660e94d85fde24f504cc9d4375d42192e84a (diff) | |
text-input: document behavior regarding multiple text-inputs
Currently protocol does not specify what should happen if multiple
text-inputs are created by same client, which is why this is more or
less undefined behavior currently in compositor implementations.
If client has created more than one text-input objects and surface owned
by the client is focused, then compositor must send enter event to all
text-input objects, in case of enable request however only one
text-input must be enabled per client per seat.
Signed-off-by: Bhushan Shah <bshah@kde.org>
Diffstat (limited to 'unstable/linux-explicit-synchronization')
0 files changed, 0 insertions, 0 deletions