Send typing notification

[bmarty]

Type of change

• Feature
• Bugfix
• Technical
• Other :

Content

Send typing notification.
Note: there will be a setting to disable typing notification, it's tracked by #2241.

Motivation and context

Closes #2240

Screenshots / GIFs

NA

Tests

• Start typing in a room and observe with another session and using a client which supports rendering of typing notification that the typing notification is displayed.

Tested devices

• Physical
• Emulator + Ele Web.
• OS version(s):

Checklist

• Changes have been tested on an Android device or Android emulator with API 23
• UI change has been tested on both light and dark themes
• Accessibility has been taken into account. See https://github.com/element-hq/element-x-android/blob/develop/CONTRIBUTING.md#accessibility
• Pull request is based on the develop branch
• Pull request includes a new file under ./changelog.d. See https://github.com/element-hq/element-x-android/blob/develop/CONTRIBUTING.md#changelog
• Pull request includes screenshots or videos if containing UI changes
• Pull request includes a sign off
• You've made a self review of your PR

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[github-actions]

📱 Scan the QR code below to install the build (arm64 only) for this PR.

If you can't scan the QR code you can install the build via this link: https://i.diawi.com/Ai9rJC

[jmartinesp]

The changes LGTM, and I'm glad you found the onTyping API of the RTE!

There's only one thing that bothers me, the Rust SDK doesn't seem to be sending a 'no longer typing' message to the server when we set call typingNotice(false). If I set up the debugger I can see the false value arriving and being sent to the Rust SDK, but when I look at the other client I can still see the typing... status until the 4s timeout happens.

It's not something we can fix in this PR, so we should merge it as is, but I think we should also investigate what's wrong with the SDK behaviour.

[bmarty]

matrix-org/matrix-rust-sdk#3064 has been created to track the observed issue.

[bmarty]

There's only one thing that bothers me, the Rust SDK doesn't seem to be sending a 'no longer typing' message to the server when we set call typingNotice(false). If I set up the debugger I can see the false value arriving and being sent to the Rust SDK, but when I look at the other client I can still see the typing... status until the 4s timeout happens.

Actually I think it's a feature of Element Web; see matrix-org/matrix-rust-sdk#3064 (comment)

If you use another client, for instance Element Android, the typing notification disappears faster when the other user stops typing.