element-hq / element-hq/element-ios
even after scrollback has loaded, the jump to bottom button claims you have N unread messages
Open
A-Timeline
O-Occasional
S-Major
T-Defect
- Dominant language
- Swift
- Stars
- 1.8k
- Forks
- 544
- PR merge metrics
- PR metrics pending
Description
feels like unread badge counts are massive lagging behind reality.
Contributor guide
Research direction
No file, test, or entry point is named. Start by reproducing the issue after scrollback has loaded and compare the jump-to-bottom button's unread count with the actual unread messages; done means the badge reflects the current count.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100