element-hq / element-hq/element-web

Wrong thread displayed after opening from a notification

Open
#24,305 4 comments 0 reactions 0 assignees View on GitHub
A-Notifications A-Threads O-Occasional S-Major T-Defect
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Looking at another window. Not sure, but probably the relevant room was already open, with the old thread open in the sidebar.
2. A notification pops up for a new thread I have not opened (in the same room)
3. Click the notification
4. Element Web appears, but the old thread is visible
5. When I click the new thread in the main timeline, it does not appear on the right - the display flickers but the old thread re-appears.

### Outcome

#### What did you expect?
I expected to be switched to the new thread when I clicked the notification.
I expected to be able to change thread by clicking on it in the main timeline.

#### What happened instead?
I seem to be stuck looking at the old thread.

### Operating system

Ubuntu 22.04

### Browser information

Furefox 109.0

### URL for webapp

https://develop.element.io

### Application version

Element version: 0990a0dcdd96-react-056fec844ff0-js-64197bf4db64 Olm version: 3.2.12

### Homeserver

matrix.org

### Will you send logs?

Yes

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue on https://develop.element.io using the notification click, main timeline, and existing sidebar thread steps. Trace how notification opening and main-timeline thread selection update the displayed thread; done means the notification opens the new thread and selecting another thread replaces the old one without flickering back.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.