1. 03 Nov, 2020 1 commit
    • Bhushan Shah's avatar
      text-input: document behavior regarding multiple text-inputs · 4ed0cafe
      Bhushan Shah authored and Bhushan Shah's avatar Bhushan Shah committed
      
      
      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>
      4ed0cafe
  2. 30 Jul, 2018 1 commit