search

telegramdesktop / tdesktop

Telegram Desktop messaging app
https://desktop.telegram.org/
Other
26.33k stars 5.23k forks source link

Scroll up (back) stops as if it reached beginning, no indication of further loading #27770

Open php4fan opened 7 months ago

php4fan commented 7 months ago

Steps to reproduce

  1. Open a chat that has many years of history with several message per day on average
  2. scroll up by dragging the scroll bar, as much as you can, as fast as you can

Expected behaviour

Whenever you reach a point where more history needs to be loaded, there should be an indication that it's loading. A spinning icon or something. It should never look like you have reached the beginning of the chat (or of what is available), unless you actually reach the beginning. If it's loading, it should say so. If there's more data but it's not being loaded for some reason, it should say so and why. If there's something I need to do in order to scroll further into the past (even if that's just to wait), it should say so.

Actual behaviour

Soon enough it will reach a point where you can't scroll further up, nothing seems to be loading, and no matter how many times you retry by scrolling a little bit down and then up again, it doesn't allow you to go any further, but there's no indication that it's loading. So, you would naturally assume that you have either reached the true beginning of the chat history, or that Telegram only stores history up to a point.

But instead, if you keep trying for a very long time (about a minute), or perhaps even just wait and then retry, it will eventually load more. You basically never know whether there's more or not.

Operating system

Manjaro Linux

Version of Telegram Desktop

4.16.6

Installation source

Static binary from official website

Crash ID

No response

Logs

No response

github-actions[bot] commented 1 month ago

Hey there!

This issue was inactive for a long time and will be automatically closed in 30 days if there isn't any further activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

php4fan commented 1 month ago

The issue still exists. (and once again, I suggest you kill the stupid bot)