Virtual keyboard (zwp-virtual-keyboard-v1) — interest in a standalone PR?

[nico4348]

Hi! I hit the need for virtual keyboard support while working around another issue (wanted auto-paste from a clipboard manager, had to use ydotool through /dev/uinput instead).

Noticed this is part of milestone 17 in DESIGN.md alongside text-input and input-method. Would a standalone PR implementing just zwp-virtual-keyboard-v1 be welcome as a first step, or do you prefer the full milestone 17 landed together?

Also open to any design or security preferences you already have in mind — virtual keyboard lets any client inject keystrokes so I figure you might want to restrict which clients can use it.

[malbiruk]

Yes, those milestones are pretty much optional. On security aspect if you can take inspiration from Niri as per discussion here #25 I'd appreciate the PR.

[malbiruk]

So if you want to tackle this, I think the implementation of zwp-virtual-keyboard-v1 should be bundled with wp_security_context_v1, add a restricted field on ClientState in state/mod.rs and filter closures for virtual keyboard.

Let me know if you'd like to take this on with that scope, or if you'd prefer I prioritize it on my end.

[nico4348]

Already took this on — opened #47 with the exact scope you described (virtual-keyboard bundled with security-context, restricted field on ClientState, filter closures). Tested with wtype end-to-end.