Batching text input protocol changes

Pekka Paalanen ppaalanen at
Tue Feb 18 08:12:11 UTC 2020

On Mon, 17 Feb 2020 19:58:43 +0100
Dorota Czaplejewicz <dorota.czaplejewicz at> wrote:

> Hi all,
> over the past month, the zwp_text_input_v3 protocol has moved to real
> devices and had seen unprecedented usage. Together with that, it also
> got a reality check, from which it didn't come unscathed. There are
> some issues identified:
> - a hint that there's no need for an on-screen keyboard
> - allow deleting text even when surrounding text is unknown
> - making it harder for compositors to send uninformed updates
> - possibly graceful switching within text inputs
> - sending control events (submit, next field, undo) to gain
> independence from a virtual keyboard protocol
> I might have left something out.
> Since they are all relatively unrelated, they can thankfully be
> discussed separately. But merging them in separately would create
> needlessly many combinations of possible supported versions.
> A new integration branch on gitlab would keep related merge requests
> on the wayland-protocols repo, and it could be merged as one large
> update once it's sufficiently hardened. Or is there another way to do
> this?

Hi Dorota,

sounds like you have a good reason to have an upstream branch like
that, so that the work in progress won't stop the master branch from
releasing. I would be fine with that.

Another way could be to start a new major version XML file, and exclude
it from install by default. No-one could use it until you make it
installable, so there would be no need to maintain implementations of
the intermediate steps.

Mind the wayland-protocols governance rules.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the wayland-devel mailing list