-
Notifications
You must be signed in to change notification settings - Fork 711
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The read marker is stuck in the past #8268
Comments
may be related to element-hq/element-ios#7420 |
When you use "Jump to bottom" button, it's made on purpose to not make your read marker updated as you are still not seing the messages in between. If you want to unstuck, just use the "jump to unread" close button. |
The read marker should be updated at the most recent event visible before I use "Jump to bottom". In my video, the read marker should be moved to the "asd" message to prevent me from jumping back to the past. There are several issues here:
|
Ah yes true, I had misunderstood the issue. |
Steps to reproduce
1- read all messages (reset a potential read marker by dismissing the "Jump to unread" banner)
2- navigate outside the room
3- send with another room member several messages (> 30), enough to not display the last read message
4- open again the room, the "Jump to unread" banner is displayed : OK
5- click on this banner, the timeline jump to the first unread message: OK (the unread messages marker may be displayed outside the screen just at the top. Scroll up to see it)
6- Jump back to live position by clicking on the icon displayed at the bottom right.
Outcome
What did you expect?
The read marker should be updated. The "jump to unread" banner should disappear if all messages have been read
What happened instead?
The read marker is stuck in the past, the "jump to unread" banner is still visible
Your phone model
No response
Operating system version
No response
Application version and app store
No response
Homeserver
No response
Will you send logs?
No
Are you willing to provide a PR?
Yes
The text was updated successfully, but these errors were encountered: