I find this warning annoying and most of the time useless. I always end up clicking "Join here" anyway.
Duplicate session
You are trying to join a conversation while having an active session in another window or device.
This is currently not supported by Nextcloud Talk. What do you want to do?
So this is my proposal to improve this:
let's say that:
- I have a tab open somewhere and I joined conversation A in that tab 1;
- I have talk open in tab 2 and i click on conversation A there too;
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
ma12-co
All 5 comments
Should be on https://github.com/nextcloud/spreed ?
skjnldsv
on 14 Oct 2020
Should be on https://github.com/nextcloud/spreed ?
:man_facepalming:
ma12-co
on 14 Oct 2020
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.
jancborchardt
on 14 Oct 2020
nickvergessen
on 14 Oct 2020
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.
This is scheduled for when developers have time.
nickvergessen
on 14 Oct 2020
Related issues
q-wertz
·
3Comments
danxuliu
·
3Comments
pilsnerbeer
·
3Comments
mario
·
3Comments
nickvergessen
·
3Comments
Most helpful comment
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.