-
Notifications
You must be signed in to change notification settings - Fork 435
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
Better duplicate session UX #4366
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Seems like a good improvement – warning only when necessary. It's then also needed to have this warning on mobile too, since currently you can end your own calls by opening the same conversation (even only the chat) on mobile, without getting informed why. Of course the best UX would be if you could just view a conversation with as many devices as you like. And that opening a chat where you are already active in a call will show you the chat, but not interrupt the call. |
This is scheduled for when developers have time. |
I find this warning annoying and most of the time useless. I always end up clicking "Join here" anyway.
So this is my proposal to improve this:
let's say that:
CASE 1 (most of the time)
User is not participating to a call in tab 1
=> Just join the conversation in tab 2, without any warning and display the "You joined the conversation in another window or device." notice in tab 1;
We could also change the title of tab 1 into
duplicate session
so that if things get messy one can easily see at a glance which tabs are safe to close.CASE 2
User had previously joined a call in tab 1
=> Show a warning that says that there's a call undergoing in conversation A in some other tab, and joining here would interrupt the call.
Do you see any drawbacks with this approach?
cc @nextcloud/designers
The text was updated successfully, but these errors were encountered: