element-hq / element-hq/element-call

Kick reason is sometimes absent for federated calls

Open
#2,336 1 comment 0 reactions 0 assignees View on GitHub
T-Defect
Dominant language
TypeScript
Stars
996
Forks
213
Avg merge
1d 6h
Merged PRs (30d)
54

Description

### Steps to reproduce

1. Set up an Element Web to allow guest links
2. Create a public room & start a video call in it
3. Copy the guest join URL and have a guest join it (unsure if the guest needs to be on a different homeserver)
4. Use that link to join the call
5. Have the creator of the room kick the joined user with a reason

### Outcome

#### What did you expect?
The Element Call SPA for the guest user should show the kick reason, like so:

![image](https://github.com/element-hq/element-call/assets/3271094/422bbee4-1202-4ce2-b312-2cd318193125)

This does happen when the room the guest is kicked from is a knock-access room or a public video room.

#### What happened instead?
No kick reason is shown:

![image](https://github.com/element-hq/element-call/assets/3271094/aa6f7ed9-92fb-49eb-83fc-b9843580a91d)

### Operating system

Fedora

### Browser information

Firefox version 125

### URL for webapp

Development version (5284479e)

### Will you send logs?

No

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in the Element Call SPA using the guest-link flow described, comparing a public room with a knock-access room and checking whether the guest is on another homeserver. Trace how the kick reason is received and displayed for federated calls; done means the guest sees the creator's reason consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
distributed-systems, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.