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

User can't mark "Direct Messages" as unread #27274

Closed
danceganse opened this issue Nov 16, 2022 · 2 comments · Fixed by #32939
Closed

User can't mark "Direct Messages" as unread #27274

danceganse opened this issue Nov 16, 2022 · 2 comments · Fixed by #32939

Comments

@danceganse
Copy link

danceganse commented Nov 16, 2022

Description:

If I want to mark a chat as unread that I have actively open won't work. The chat is only marked as unread for a second and after that the chat is marked as read. But I can mark a chat as unmarked if I don't have it actively open.

Steps to reproduce:

  1. Open the chat with another user
    Screenshot from 2022-11-16 08-30-06
  2. Click on "Mark Unread"
    Screenshot from 2022-11-16 08-32-16

Expected behavior:

The user is marked as unread.

Actual behavior:

For one second the user is marked as unread:
Screenshot from 2022-11-16 08-36-13
but after the second it looks like this:
Screenshot from 2022-11-16 08-37-59

Server Setup Information:

  • Version of Rocket.Chat Server: 5.3.1
  • Operating System: Ubuntu 20.04
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: v14.19.3
  • MongoDB Version: 5.0.13

Client Setup Information

  • Desktop Browser Version: Google Chrome (107.0.5304.110-1), Mozilla Firefox (106.0.5)
  • Operating System: Ubuntu 22.04.1 LTS
@danel1
Copy link

danel1 commented Nov 25, 2022

@ggazzo We have the same problem. See browser console log attached.
27274.txt

@danceganse
Copy link
Author

The problem still exists with version 5.4.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants