element-hq / element-hq/element-web

When an event contains `is_falling_back: false`, the message preview thinks it's a threaded reply

Open
#26,147 1 comment 0 reactions 0 assignees View on GitHub
A-Message-Previews A-Replies A-Threads O-Occasional S-Minor T-Defect
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Send a message
2. Have someone else *reply* to it (using Element Web)
3. Observe `is_falling_back: false` in event source
4. Observe message preview
5. Observe main timeline

### Outcome

#### What did you expect?

The event to show up as a not-reply.

#### What happened instead?

![image](https://github.com/vector-im/element-web/assets/1190097/b538eba4-b01d-4a6f-be88-5d59706706ee)
![image](https://github.com/vector-im/element-web/assets/1190097/a2aac92e-ea9e-4287-a668-1b78fb38dcbc)
![image](https://github.com/vector-im/element-web/assets/1190097/fc34ab92-8d01-4cdc-bf21-3ae435635719)

### Operating system

Windows 11

### Application version

Element Nightly version: 0.0.1-nightly.2023090801 Olm version: 3.2.14

### How did you install the app?

The Internet

### Homeserver

t2l.io

### Will you send logs?

No

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue with an event whose source contains `is_falling_back: false`, then trace how the message preview classifies replies. Done means the preview shows the event as a non-reply while the main timeline remains correct.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.