From fb888ba9abd010ff01d7df5554094ce234726081 Mon Sep 17 00:00:00 2001 From: Aarya Patil Date: Tue, 6 Aug 2024 07:25:37 +0000 Subject: [PATCH] docs: Update typing indicators documentation. Update typing_indicators.md to reflect current implementation. Fixes #30665. --- docs/subsystems/typing-indicators.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/subsystems/typing-indicators.md b/docs/subsystems/typing-indicators.md index d23782f885..f7eb00cf70 100644 --- a/docs/subsystems/typing-indicators.md +++ b/docs/subsystems/typing-indicators.md @@ -11,8 +11,8 @@ the Zulip web app, and our main audience is developers who want to understand the system and possibly improve it. Any client should be able follow the protocol documented here. -Right now typing indicators are only implemented for direct -message conversations in the web app. +Typing indicators are implemented for both direct message conversations +and channel conversations in the web app. There are two major roles for users in this system: @@ -102,6 +102,10 @@ potential recipients of the message. The event type for that payload is `typing`. See the function `do_send_typing_notification` in `zerver/actions/typing.py` for more details. +For channel typing notifications, the server also handles the logic +for determining which users should receive the typing events based +on channel subscribers. + ## Receiving user When a user plays the role of a "receiving user," the client handles