Skip to content

fix: remove the correct composing timeout on new chat state events

Nicoco requested to merge nicoco/gajim:fix-composing-timeout into master

My apologies, while investigating #11418 (closed) I noticed that this was a bug I introduced. It rarely has a visible effect, but it is not correct, eg:

28/02/2023 20:37:39 (I) gajim.c.m.chatstate        (localhost) Recv: Chatstate.COMPOSING - xxx@signal.localhost/slidge
28/02/2023 20:37:41 (I) gajim.c.m.chatstate        (localhost) Recv: Chatstate.ACTIVE - xxx@signal.localhost/slidge
28/02/2023 20:38:09 (I) gajim.c.m.chatstate        (localhost) Automatically switching the chat state of xxx@signal.localhost/slidge (localhost) to ACTIVE

It shouldn't "automatically switch..." since the Recv: Chatstate.ACTIVE part should have cancel the timer.

Merge request reports