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

Element refuses to consider a room read #25204

Closed
bjherbison opened this issue Apr 25, 2023 · 1 comment
Closed

Element refuses to consider a room read #25204

bjherbison opened this issue Apr 25, 2023 · 1 comment
Labels

Comments

@bjherbison
Copy link

Steps to reproduce

  1. Visit https://chat.mozilla.org/#/room/#firefox:mozilla.org .
  2. View a message https://matrix.to/#/!OjiTSQTpPWGpfDenKT:mozilla.org/$5UsDgcRFAc56OKwhFLa1tctVj0S17PWOCVcOtuqc6lo?via=mozilla.org&via=matrix.org&via=privacytools.io which starts a thread.
  3. View the thread. Scroll to the top and bottom of the thread.
  4. Leave the room.
  5. Enter the room again.
  6. View the thread list -- only one thread has a dot, the most recent.
  7. Scroll to the top and bottom of the thread.
  8. Leave the room again.
  9. Enter the room again.
  10. In the room menu mark the room as read.
  11. Leave the room again.
  12. Enter the room again.
  13. In the room menu mark the room as read.
  14. Leave the room again.

Outcome

What did you expect?

After reading everything the room had an unread count of zero and no threads marked as having unread content.

What happened instead?

The room showed up as having two unread messages until after the second time I selected Mark as Read. And then a minute later, while composing this message, the room now has two read again. And the thread has a dot again.

Operating system

Linux

Browser information

Firefox Nightly

URL for webapp

https://chat.mozilla.org/#/room/#firefox:mozilla.org

Application version

Element version: 1.11.30 Olm version: 3.2.12

Homeserver

https://chat.mozilla.org/

Will you send logs?

Yes

@t3chguy
Copy link
Member

t3chguy commented Apr 25, 2023

Closing in favour of #24392

@t3chguy t3chguy closed this as completed Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants