Telegram automatically jumps to the bottom of the chat and marks all messages read

[Hobbix]

Steps to reproduce

Telegram automatically jumps to the bottom of the chat and marks all messages read.

When you read some groups, Telegram automatically goes to the bottom of the chat and marks all messages read.
This is a floating bug that happens quite randomly. I've been trying to figure out why this happens for a long time and I think I've found the reason.

Some Telegram groups have moderator bots that automatically block some users (e.g. for incorrect user name), swear words, display a welcome message in the group when a new user joins the group, delete informational messages when a new member joins the group, remind you of the group rules (sometimes with buttons for quick jump) and so on.
When a moderator bot spams these messages too often, it very often causes the chat to automatically jump to the end of the chat to the last message.
As a result, if you were reading messages in a group, all unread messages are automatically marked as read, you lose the position in the chat you were reading, and you are forced to scroll up and find the place you were reading before jumping down.

You spend a long time looking for the place where you stopped reading, and then the chat jumps down again. This bug is very annoying.

Expected behaviour

When you read any group, the chat should not jump to the last post, marking all posts as read.

Actual behaviour

When you read any group, the chat will jump to the last post, marking all posts as read.

Operating system

Windows 10

Version of Telegram Desktop

4.12.2

Installation source

Static binary from official website

Crash ID

No response

Logs

No response

[benhacka]

I confirm that. There is usually a fake message at the end that you have joined the group. The only chance to view such groups in any way is to periodically save some messages in saved and after another scroll down go to them through "saved messages" in the group itself.

upd - some logs for this case:
In the normal logs:

QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter

In the debug logs also see:

JumpToEnd(..., ..., [FALSE]): Loading up before 0. (history_widget.cpp : 25)

tdesktop/Telegram/SourceFiles/history/history_widget.cpp

Line 2000 in 2f0b50c

DEBUG_LOG(("JumpToEnd(%1, %2, %3): "

Unfortunately, due to the huge number of lines in the debug logs, it is impossible to understand what provokes this behavior. But in all these cases, the client is trying to send some kind of acks to the server. So It seems that this happens in groups with manual confirmation by admins, but bots confirm them and do this many times for the same account and because of this, there is an event that you "joined" the group on each such wave of confirmations.

[github-actions]

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!

[Hobbix]

The issue hasn't been resolved yet

[github-actions]

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!

[Hobbix]

The issue hasn't been resolved yet