element-hq / element-hq/element-web

Inconsistent unread chats between EXA and Web

Open
#29,815 0 comments 0 reactions 0 assignees View on GitHub
A-Room-List O-Occasional S-Minor T-Defect Z-Labs
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Filter room list for unread chats on EXA and Web
2. Compare

### Outcome

#### What did you expect?
Same chats

#### What happened instead?
Different chats (EXA is a superset of Web)

Android | Web
---------|--------
![Image](https://github.com/user-attachments/assets/a1cd80e6-a555-4bd9-be8b-5977e31197b7) | ![Image](https://github.com/user-attachments/assets/348d4ccd-cbd2-4618-bc62-ce291c2e58f8)

### Operating system

Windows 11 and Android 14

### Browser information

Version 135.0.3179.85

### URL for webapp

https://develop.element.io

### Application version

Element version: 5e7b58a72238-js-19b1b901f575 Crypto version: Rust SDK 0.11.0 (f2e32d4), Vodozemac 0.9.0

Element X Android version: 25.04.2-nightly

### Homeserver

element.io

### Will you send logs?

Yes

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the unread-chat filter comparison on https://develop.element.io and compare it with Element X Android 25.04.2-nightly using the stated Windows 11 and Android 14 setup. Trace how each client determines unread rooms; done means both clients show the same chats, with Web matching EXA rather than omitting rooms.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.