Add start delay for typing indicator
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
When a message is written and sent very quickly, another user hides the typing indicator later than the message is received. Moreover, sometimes the indicator appears later than the typed message was received.
The result is:
- You have a message from Alice!
- Hey, Alice is typing to you (already received message message)
- Alice's stopped typing
Describe the solution you'd like
Add a delay before starting the typing indicator. For example, for 5 or 10 seconds.
With slow messaging:
- User is typing
- Wait for 5 sec
- Send
startTypingand launch the interval - User has sent the message
- Send
stopTyping
With fast messaging:
- User is typing
- Wait for 5 sec
- User has sent the message
- Nothing happened
Describe alternatives you've considered
An alternative solution is to make the same on the receiver side.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the JavaScript typing-indicator flow around the startTyping and stopTyping events described in the issue. Verify how the current interval is launched and cancelled, then confirm that fast messages send neither event while slower typing starts the indicator only after the delay and stops it after sending.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100