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

Private chat gets disabled if opponent shortly left #10145

Closed
iznakurnozh opened this issue Jul 29, 2020 · 4 comments
Closed

Private chat gets disabled if opponent shortly left #10145

iznakurnozh opened this issue Jul 29, 2020 · 4 comments

Comments

@iznakurnozh
Copy link

Describe the bug
When your opponent leaves the conference the private chat with her gets disabled and one cannot write anymore. If the opponent comes back the writing option stays disabled.

To Reproduce
Steps to reproduce the behavior:

  1. Start a private chat with another user
  2. Write something in the chat
  3. Another user leaves -> writing option gets disabled
  4. Another user comes back (with the same user name)
  5. Writing option remains unavailable

Expected behavior
When your opponent comes back the writing option should be enabled again

Desktop (please complete the following information):

  • OS: Windows 10 pro
  • Browser Firefox 78.0.2 (64-Bit)
  • Version [e.g. 22]
@matiasilva
Copy link
Collaborator

This is likely due to how your frontend creates "users" and thus the HTML5 client sees them as different people. What frontend are you using?

@iznakurnozh
Copy link
Author

iznakurnozh commented Jul 29, 2020

You are right, when the opponent writes sth - another instance of a private chat gets created. It was the greenlight attending with an invitation link. However, it does not occur when just reloading page, but only when the opponent loggs out or clicks "back" in the browser and reenters from there.

@matiasilva
Copy link
Collaborator

Ah, I just realized this was you. I think I misunderstood this issue so I'm reopening it :)

@stale
Copy link

stale bot commented Jun 7, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status: stale label Jun 7, 2022
@stale stale bot closed this as completed Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants