|
|
@ -1,10 +1,10 @@
|
|
|
|
Typing Notifications
|
|
|
|
Typing Notifications
|
|
|
|
====================
|
|
|
|
====================
|
|
|
|
|
|
|
|
|
|
|
|
Users often desire to see when another user is typing. This can be achieved
|
|
|
|
Users may wish to be informed when another user is typing in a room. This can be
|
|
|
|
using typing notifications. These are ephemeral events scoped to a ``room_id``.
|
|
|
|
achieved using typing notifications. These are ephemeral events scoped to a
|
|
|
|
This means they do not form part of the `Event Graph`_ but still have a
|
|
|
|
``room_id``. This means they do not form part of the `Event Graph`_ but still
|
|
|
|
``room_id`` key.
|
|
|
|
have a ``room_id`` key.
|
|
|
|
|
|
|
|
|
|
|
|
.. _Event Graph: `sect:event-graph`_
|
|
|
|
.. _Event Graph: `sect:event-graph`_
|
|
|
|
|
|
|
|
|
|
|
@ -37,7 +37,8 @@ to inform the server that the user has stopped typing.
|
|
|
|
Server behaviour
|
|
|
|
Server behaviour
|
|
|
|
----------------
|
|
|
|
----------------
|
|
|
|
|
|
|
|
|
|
|
|
Servers MUST emit typing EDUs in the following form::
|
|
|
|
Servers MUST emit typing EDUs in a different form to ``m.typing`` events which
|
|
|
|
|
|
|
|
are shown to clients. This form looks like::
|
|
|
|
|
|
|
|
|
|
|
|
{
|
|
|
|
{
|
|
|
|
"type": "m.typing",
|
|
|
|
"type": "m.typing",
|
|
|
|