Stuck notifications when there's no new message after a thread

[anarute]

Steps to reproduce

When a thread is the last message of a room and there's new messages inside the thread, marking the room as read doesn't work, the notification remains there until there's a new message in the room outside the thread.

To reproduce:

1 - create a thread in the last message of a room
2 - go to another room and ask someone to write a message inside the room
3 - mark the room as read

Outcome

What did you expect?

Marking the room as read would remove any notification for that room.

What happened instead?

The notification badge gets stuck in the room until someone writes a new message in the room outside the thread.

Operating system

Fedora

Browser information

Chromium 112.0.5615.165 (Official Build) Fedora Project (64-bit)

URL for webapp

No response

Application version

Element version: 1.11.36 Olm version: 3.2.14

Homeserver

No response

Will you send logs?

No

[t3chguy]

Does the thread list top right have an unread dot on it?

mark the room as read

Can you be more specific, there's multiple ways to do this

If you don't send logs and notifications debug unfortunately there isn't enough here to go on.

[anarute]

Thank you for the quick reply, I've recorded a video that reproduces it, let me know if it helps and if you need more info:

Studio_Project_V1.mp4

Btw this only happens if another user creates the thread, if I'm the one creating I can mark the room as read.