element-hq / element-hq/element-x-android
Read receipts and reactions cause excessive dead space in the timeline
- Dominant language
- Kotlin
- Stars
- 2.4k
- Forks
- 624
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 149
Description
This is a subjective issue, but to me it feels like the read receipts should be tied to the bottom of the message bubble and not the bottom of the reactions, otherwise the timeline ends up with big gaps like this (please excuse the crude redactions)

The only minor concern I could see with this approach would be a very wide message with lots of reactions potentially overlapping the receipts on the right, but that could be prevented by either limiting the width of both sides such that they never overlap, or pushing the read receipts down a bit if an overlap would occur
Contributor guide
Assessment
This issue has not been assessed yet.