PrivateCoffee/element-web
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 3

Work around a Jitsi bug with display name encoding (#22525)

Browse source
This commit is contained in:
Robin 2022-06-10 12:21:49 -04:00 committed by GitHub
parent 0fd1bc7f5a
commit 867fc30ebf
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
src/vector/jitsi/index.ts
View file

@ -394,6 +394,16 @@ function joinConference(audioDevice?: string, videoDevice?: string) {
// fires once when user joins the conference // fires once when user joins the conference
// (regardless of video on or off) // (regardless of video on or off)
meetApi.on("videoConferenceJoined", () => { meetApi.on("videoConferenceJoined", () => {
// Although we set our displayName with the userInfo option above, that
// option has a bug where it causes the name to be the HTML encoding of
// what was actually intended. So, we use the displayName command to at
// least ensure that the name is correct after entering the meeting.
// https://github.com/jitsi/jitsi-meet/issues/11664
// We can't just use these commands immediately after creating the
// iframe, because there's *another* bug where they can crash Jitsi by
// racing with its startup process.
if (displayName) meetApi.executeCommand("displayName", displayName);
// This doesn't have a userInfo equivalent, so has to be set via commands
if (avatarUrl) meetApi.executeCommand("avatarUrl", avatarUrl); if (avatarUrl) meetApi.executeCommand("avatarUrl", avatarUrl);
if (widgetApi) { if (widgetApi) {