Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle empty Jitsi default URL #5837

Closed
aringenbach opened this issue Mar 16, 2022 · 0 comments · Fixed by #5894
Closed

Handle empty Jitsi default URL #5837

aringenbach opened this issue Mar 16, 2022 · 0 comments · Fixed by #5894
Assignees
Labels
A-Jitsi O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@aringenbach
Copy link
Contributor

Your use case

Element client should allow to handle the absence of a default Jitsi URL and display an error message if a client tries to start a Jitsi call with no URL.

This would allow forks to effectively disable entirely Jitsi calls without providing a fake URL (and especially avoid starting a call by mistake on the standard element Jitsi server).

Have you considered any alternatives?

No

Additional context

No

@aringenbach aringenbach added the T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements label Mar 16, 2022
@aringenbach aringenbach self-assigned this Mar 16, 2022
@stefanceriu stefanceriu added A-Jitsi S-Minor Impairs non-critical functionality or suitable workarounds exist O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Jitsi O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants