tdesktop icon indicating copy to clipboard operation
tdesktop copied to clipboard

Emoji History Is Formed Only from Explicitly Selected Emojis

Open stanislawru opened this issue 4 years ago • 7 comments

Steps to reproduce

  1. Open any chat.
  2. Visually select any emoji from the emoji panel and then send it to that chat, better a few times.
  3. See that emoji in the list of recent emojis.
  4. Type any other emoji manually as :emojiname: or paste it from the clipboard and then send it to the chat, better a few times.
  5. See that second emoji has not appeared in the list of recent emojis.

Expected behaviour

The emoji history must be formed not only from the emojis visually selected from the emoji panel but also from those that were typed manually or pasted from the clipboard.

Actual behaviour

Emojis that were typed manually or pasted from the clipboard do not appear in the list of recent emojis.

Operating system

Windows 7, 8.1 and 10

Version of Telegram Desktop

3.0.1

Installation source

Static binary from official website

Logs

No response

stanislawru avatar Sep 09 '21 09:09 stanislawru

or pasted from the clipboard

I don't think it's a good idea. Imagine you pasted a big text with a lot of emojis, boom, all of these emojis will be in your list of recent emojis, removing emojis you actually using regularly.

ilya-fedin avatar Sep 09 '21 10:09 ilya-fedin

OK, let's limit the fix to: emojis that were typed manually as :emojiname: should appear in the list of recent emojis. This works well in the Android app.

stanislawru avatar Sep 09 '21 10:09 stanislawru

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!

stale[bot] avatar Mar 09 '22 02:03 stale[bot]

“We therefore assume that the user has lost interest or resolved the problem on their own”, – really? :open_mouth: I am not a developer, so cannot fix the issue myself. And I consider unfair to close the issue just because there is no developer to fix it. :disappointed:

stanislawru avatar Mar 09 '22 12:03 stanislawru

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[bot] avatar Sep 06 '22 02:09 github-actions[bot]

“We therefore assume that the user has lost interest or resolved the problem on their own”, – really? :open_mouth: I am not a developer, so cannot fix the issue myself. And I consider unfair to close the issue just because there is no developer to fix it. :disappointed:

stanislawru avatar Sep 10 '22 09:09 stanislawru

Yeah, really. A lot of people losing interest in issues after some time. If you're not, relax and just answer the bot for it to not to close the issue.

ilya-fedin avatar Sep 10 '22 09:09 ilya-fedin

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[bot] avatar Mar 11 '23 01:03 github-actions[bot]

“We therefore assume that the user has lost interest or resolved the problem on their own”, – really? 😮 I am not a developer, so cannot fix the issue myself. And I consider unfair to close the issue just because there is no developer to fix it. 😞

stanislawru avatar Mar 11 '23 07:03 stanislawru

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[bot] avatar Sep 09 '23 01:09 github-actions[bot]

“We therefore assume that the user has lost interest or resolved the problem on their own”, – really? 😮 I am not a developer, so cannot fix the issue myself. And I consider unfair to close the issue just because there is no developer to fix it. 😞

stanislawru avatar Sep 09 '23 13:09 stanislawru

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[bot] avatar Mar 10 '24 01:03 github-actions[bot]

“We therefore assume that the user has lost interest or resolved the problem on their own”, – really? 😮 I am not a developer, so cannot fix the issue myself. And I consider unfair to close the issue just because there is no developer to fix it. 😞

stanislawru avatar Mar 10 '24 06:03 stanislawru