Open a conference in a new tab

[henrybrink]

This change is introducing the issue desribed in #78

[SergioComeron]

Hi @henrybrink ,
I'm testing your branch.
I've observed that when enter to the session in a new tab the avatars are not visible. However with the same configuration when opening it embedded, the avatars are seen. The same thing happens to you in your tests?
new tab:

embedded:

[henrybrink]

Yes @SergioComeron,
Jitsi seems to not support passing a avatarURL via the URL-Parameters, but the documentation about this is not really complete. I tried to append the URL via "userInfo.avatarURL", but this did not work for me. Maybe this should be included in the hint in the settings for the selection which methods are available for the user to open the conference in.

[henrybrink]

While Jitsi really seems to have no support passing the url for the avatar via the URL, it is however supported via the JWT-Token, so when an application is using JWT the avatar will displayed in the conference regardless of the mode the user is viewing the conference. The avatar will even get loaded, when the Server is not accepting the JWT-Token, like meet.jit.si, but then the user can't join the room because of the invalid authentication.

[SergioComeron]

Hi @henrybrink ,
all the tests that I have been doing to pass the avatar through the jwt token so far have not been successful and I have never been able to display the avatar via url. Did you get it?

[SergioComeron]

Sorry,
I just saw that the problem is with access permissions to the images that I use as an avatar.

[henrybrink]

Okay, no problem. I also had some issues while testing this.

[aczerzuh]

Hi, is there any update to this PR? Does anything need to be implemented in order to be accepted into the main repo? In our case we need that feature cause our weblogin has a CSP rule which blocks the iframe rendering.
Best wishes,
adrian

[SergioComeron]

hi aczerzuh,
To open the session in a new tab and not be embedded, it would be necessary to pass all the parameters through the url. In the last revisions that I have made about this, this option does not allow us to pass some of the parameters that we use in the sessions. This would be the reason why we don't implement the option to open the session in another tab.