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

Unread chat is marked as read if you share post from public with your comment #25843

Open
SpL1Ne opened this issue Feb 6, 2023 · 11 comments
Open
Labels

Comments

@SpL1Ne
Copy link

SpL1Ne commented Feb 6, 2023

Steps to reproduce

  1. Have chat with unread messages.
  2. Open any public
  3. Click "Share to" button.
  4. Select chat with unreaded messages.
  5. Enter any comment in field below chat list in "Share to" popup.

Expected behaviour

I guess it should be like in mobile version of telegram (checked only with android nonGP version).
In mobile telegram chat stays unreaded when you share post from public (with\without comment from user).

Actual behaviour

If you share post from public without comment from user unread chat stays unread.
If you add comment with post chat will become read.

Operating system

Win10 21H1, 19043.985

Version of Telegram Desktop

v4.6

Installation source

Static binary from official website

Logs

No response

@SpL1Ne SpL1Ne added the bug label Feb 6, 2023
@RememberTheAir
Copy link

What do you see from the desktop app when you "quick-share" something from Android to a chat that has unread messages?
I'm asking this because I've always assumed that sending any message in a private chat will automatically mark as read all past messages, and this is automatically done by the server - the client doesn't need to explicitly request to mark these messages as read. So, either this assumption is wrong (in this case, if you forward something from the android app, unread messages will not be marked as read on desktop either) or the Android app doesn't properly mark the chat as read (the messages are marked as read on desktop after you forward from Android)

@RememberTheAir
Copy link

RememberTheAir commented Feb 7, 2023

I just tested this and it seems that my assumption was wrong, so there is in fact a difference in the behavior of the two apps

@SpL1Ne
Copy link
Author

SpL1Ne commented Feb 7, 2023

if you forward something from the android app, unread messages will not be marked as read on desktop either

This one is true.
And IMO it's better when chat isn't mark as read when you share post with comment. I mean, you have actually open chat and sent message (like with forwarding messages). "Share to" with comment is one entity for me, so why should it trigger different behavior than just share post without comment.

I've always assumed that sending any message in a private chat will automatically mark as read all past messages

Well, shared post technically is "any message" but it still doesn't marks chat as read. I always assumed, that it's because of the reason I explained above.

@github-actions
Copy link

github-actions bot commented Aug 7, 2023

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!

@github-actions github-actions bot added the stale label Aug 7, 2023
@SpL1Ne
Copy link
Author

SpL1Ne commented Aug 7, 2023

Still relevant.

@github-actions github-actions bot removed the stale label Aug 8, 2023
Copy link

github-actions bot commented Feb 5, 2024

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!

@github-actions github-actions bot added the stale label Feb 5, 2024
@SpL1Ne
Copy link
Author

SpL1Ne commented Feb 5, 2024

Still relevant.

@github-actions github-actions bot removed the stale label Feb 6, 2024
Copy link

github-actions bot commented Aug 4, 2024

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!

@github-actions github-actions bot added the stale label Aug 4, 2024
@SpL1Ne
Copy link
Author

SpL1Ne commented Aug 4, 2024

Still relevant.

@github-actions github-actions bot removed the stale label Aug 5, 2024
Copy link

github-actions bot commented Feb 1, 2025

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!

@github-actions github-actions bot added the stale label Feb 1, 2025
@SpL1Ne
Copy link
Author

SpL1Ne commented Feb 1, 2025

Bump.

@github-actions github-actions bot removed the stale label Feb 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants