Skip to content
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

Jumping up to first unread clears timeline and issues error message #23736

Open
kongo09 opened this issue Nov 9, 2022 · 1 comment
Open

Jumping up to first unread clears timeline and issues error message #23736

kongo09 opened this issue Nov 9, 2022 · 1 comment
Labels
A-Timeline O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@kongo09
Copy link

kongo09 commented Nov 9, 2022

Steps to reproduce

  1. Entered a room
  2. clicked on marker to jump up to first unread message

Outcome

What did you expect?

jumping up to first unread message

What happened instead?

timeline is cleared to empty screen and error message is displayed

image

Operating system

Windows 11

Element version: 1.11.14
Olm version: 3.2.12

@andybalaam andybalaam added S-Minor Impairs non-critical functionality or suitable workarounds exist A-Timeline O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience labels Nov 10, 2022
@ThoreKr
Copy link

ThoreKr commented Nov 30, 2022

This can be reproduced in rooms with retention enabled.
If the last unread message is past the rention period and it has been purged from the server, this can happen as well.
The condition for this to happen is that either the client wasn't there to receive to messages or their have been removed from the local cache as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Timeline O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Development

No branches or pull requests

3 participants