ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
Lyude has quit [Read error: Connection reset by peer]
Leopold_ has quit [Remote host closed the connection]
Lyude has joined #wayland
lyudess has quit [Ping timeout: 480 seconds]
thevar1able1 has joined #wayland
thevar1able1 is now known as thevar1able
nerdopolis has quit [Ping timeout: 480 seconds]
zebrag has quit [Quit: Konversation terminated!]
rasterman has joined #wayland
danshick has quit [Ping timeout: 480 seconds]
<kchibisov>
If input_method sends garbage data that breaks what text_input says who is in charge of sanity checking it?
danvet has joined #wayland
<kchibisov>
We had a bug report with mutter when we were getting invalid cursor offset in text_input::preedit. Invalid as the cursor was inside utf-8 character.
dcz_ has joined #wayland
danshick has joined #wayland
rv1sr has joined #wayland
hardening has joined #wayland
___nick___ has quit []
<jadahl>
kchibisov: in general, compositors should sanity check everything from clients, but clients should arguably need less sanity checking
___nick___ has joined #wayland
<emersion>
kchibisov: iirc the proto says that indices must not be between two unicode codepoints? thus the compositor needs fixing?
<jadahl>
emersion: it doesn't seem to say very much, but one can assume that it shouldn't at least
<emersion>
maybe it was input method then
<kchibisov>
input method says even less afaics.
<jadahl>
kchibisov: can you open a bug with wayland debug logs? looking at the code it should already always convert a "unicode index" to byte index, so need a bit data to reproduce I suspect