Commit 4ed0cafe authored by Bhushan Shah's avatar Bhushan Shah Committed by Bhushan Shah

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: default avatarBhushan Shah <bshah@kde.org>
parent 3a74660e
Pipeline #223023 passed with stages
in 46 seconds