matrix-org / matrix-org/matrix-js-sdk
Call not hangup on external connection loss
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.2k
- Forks
- 704
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 40
Description
**Describe the bug**
An active call using the matrix-js-sdk (current stable version) is not hangup when an external source leads to a connection loss (e.g. browser reload).
**To Reproduce**
Steps to reproduce the behavior:
1. Start a call between two matrix-js-sdk clients
2. Reload the browser tab of client a
3. Client b stays in the call state without any chance of knowing the connection is lost
**Expected behavior**
After a short timeout the call should stop for client b.
Is there any configuration or documentation we missed?
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 reproducing the connection-loss scenario with two matrix-js-sdk clients and trace the call lifecycle when one browser tab reloads. Identify where loss detection and timeout handling belong; done means the remaining client leaves the call after a short timeout and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100