So far when KWin intercepted a key event a leave was not sent to the
Wayland surface currently having keyboard focus. This could result in
the Wayland application to start repeating keys. E.g.
- application gets key press event
- This triggers an internal window to show
- key release goes to KWin internal window
- application starts to repeat key as there is no release
With this change whenever KWin intercepts the key event e.g. due to
- internal window
- Effects grabbing key event
- Tabbox
the focused keyboard surface is set to null, thus triggering a leave
event and the client not starting to repeat the event.