* Wayland virtual keyboards and input methods :wayland:linux:
:PROPERTIES:
:ID: 7ff3d095-b9e3-4939-81be-47b5eef426ec
:CUSTOM_ID: wayland-input
:EXPORT_FILE_NAME: notes/wayland-virtual-keyboard-ime
:DESCRIPTION: Working notes on why virtual-keyboard input and input-method keyboard grabs occupy different paths in the Wayland stack.
:LOAM_KIND: note
:LOAM_STATUS: growing
:LOAM_ORDER: 40
:END:

A recurring source of confusion is that producing key events is not necessarily the same thing as participating in the input-method path. Compositors mediate both sides, and protocol choice changes what an IME can observe.

** Why I care
:PROPERTIES:
:CUSTOM_ID: why-input-methods
:END:

This question surfaced while building [[id:fca1e20c-4538-4939-ab42-0b588eb9108a][TouchDeck]], where synthetic key events need to coexist with normal text input and Rime-based composition.