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

Read message is marked as unread #25804

Open
Tracked by #24392
kittykat opened this issue Jul 14, 2023 · 5 comments
Open
Tracked by #24392

Read message is marked as unread #25804

kittykat opened this issue Jul 14, 2023 · 5 comments
Labels
A-Read-Marker Green line showing how far _you_ have read O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Regression

Comments

@kittykat
Copy link
Contributor

Steps to reproduce

  1. Receive message in DM that you're looking at
  2. Read it
  3. Navigate away

Outcome

What did you expect?

Room stays read

What happened instead?

I get an unread count for the last message that I've already read

Operating system

No response

Browser information

Chromium 114.0.5735.198 (Official Build) Arch Linux (64-bit)

URL for webapp

develop.element.io

Application version

Element version: b89b000-react-77c3a89cbc14-js-0b193f466562 Olm version: 3.2.14

Homeserver

matrix.org

Will you send logs?

Yes

@kittykat kittykat added S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Uncommon Most users are unlikely to come across this or unexpected workflow A-Read-Marker Green line showing how far _you_ have read labels Jul 20, 2023
@moodler
Copy link

moodler commented Aug 1, 2023

Confirmed, seeing this a lot (especially when the chat room has threads, I think)

@klochowicz
Copy link

I can confirm that it happens routinely to everyone on our project, and started happening when we enabled threads.

In the same way, if I click "mark messages as read" in a channel, they go back to unread within a few seconds 😭 notably the unread count can bounce back to a different number every time (numbers from today: 1, 7 , 4).

@t3chguy
Copy link
Member

t3chguy commented Aug 3, 2023

If you're going to state you're having the same issue then please also send what version you're using and logs.

@egasimus
Copy link

egasimus commented Aug 23, 2023

Confirmed, also happens to us on Element Web 1.1.37 (and previous versions) ever since we enabled threads. (Sorry for no logs.)

@klochowicz
Copy link

klochowicz commented Aug 23, 2023

If you're going to state you're having the same issue then please also send what version you're using and logs.

I'm sorry for not providing logs, it actually started working amazingly well with the recent updates when I tried to reproduce it again (even the threads get read after clicking 'mark as read').
All in all, everything works fine on my macOS client (1.11.39) now ❤️‍🔥

If I ever encounter this issue again, I'll gather the logs and open a separate ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Read-Marker Green line showing how far _you_ have read O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect X-Regression
Projects
None yet
Development

No branches or pull requests

5 participants