element-hq / element-hq/element-web

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

Open
#25,893 2 comments 0 reactions 0 assignees View on GitHub
A-Notifications O-Uncommon S-Major T-Defect
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### 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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.