Repinning of existing jitsi widget results in incorrect jitsi configurations

[kerryarchibald]

Steps to reproduce

1. In a room of 3, create a video call, join the conference, a jitsi call is created with current config
2. Unpin the call, no others in the room are in the call. (At this stage I would consider the call's lifecycle to be complete)
3. change .well-known config. set a new['im.vector.riot.jitsi'].preferredDomain
4. Back in my original room, it is not obvious to me that the room has an existing/dormant jitsi call. (Especially true when "UIFeature.widgets" is set to false, hiding the widgets section from the right panel)
5. Create a video call, the old jitsi is reused with old configuration, new preferredDomain is not used. The old jitsi will persist until explicitly removed

Outcome

What did you expect?

Behaviour of the voice/video call buttons for 2 members is in line with my expectations for calls in chat - ephemeral. I think the > 2 behaviour should align more closely.

What happened instead?

Related:
element-hq/element-web#17679

Operating system

No response

Browser information

No response

URL for webapp

No response

Application version

No response

Homeserver

No response

Will you send logs?

No