Optimize Jitsi widget message #1382
Labels
A-Jitsi
A-Widgets
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
Comments
|
Related element-hq/element-web#15718 |
|
We might also be able to get way with finally adding the accept/reject buttons to the bubble rather than trying to steer the user into the right direction. @nadonomy are there quick wins we can do on this? |
turt2live
referenced
this issue
in matrix-org/matrix-react-sdk
Jan 27, 2021
Seems to be that as part of the layout work the timing sequence for when `.getRoom().widgets` will work changed. We can get around this with `initIfNeeded` which will no-op in the worst case. This also includes a copy change to make ended conferences stop lying about where to find the widget. This is work towards https://github.com/vector-im/element-web/issues/15739
turt2live
added
O-Uncommon
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your suggestion related to a problem? Please describe.
In some situations the Jitsi widget is added to a room in preparation of future meetings. The message posted to the room however says a meeting is started and users should join. The widget can also be hidden in the sidebar and not visible "at the top of the room". This can be confusing and should be changed to more general message.
Current message:
Describe the solution you'd like
The message should notify the user that a video conference feature has been added to the room and how it can be used and not indicate that a conference has started.
The text was updated successfully, but these errors were encountered: