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

Copying emoji doesn't work as expected #2517

Closed
1 task done
mammuth opened this issue Jul 10, 2018 · 6 comments
Closed
1 task done

Copying emoji doesn't work as expected #2517

mammuth opened this issue Jul 10, 2018 · 6 comments
Labels

Comments

@mammuth
Copy link
Contributor

mammuth commented Jul 10, 2018

  • I have searched open and closed issues for duplicates

Searched for "emoji" and skimmed through all messages.
Search terms to make finding this issue easier: emoji, smiley, Emoji image of, copy paste


Bug description

When copying a message with an emoji (or just the emoji), and pasting it in the message box, not the emoji image is pasted (nor the emoji-text representation (like :+1:)), but Emoji image of 'emoji_name'

Steps to reproduce

  1. Have a past message with an emoji in it.
  2. Copy it.
  3. Paste it into the compose field.

Actual result:
Compose field contains: Emoji image of 'X'
(where x = name of the emoji (eg. muscle)

Expected result:
Compose field contains: 💪

Screenshots

image

Platform info

Signal version:
1.13.0-beta.2

Operating System:
macOS 10.13.5

Linked device version:
Android 4.23.3

Complete device info:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) SignalBeta/1.13.0-beta.2 Chrome/61.0.3163.100 Electron/2.0.1 Safari/537.36 node/8.9.3 env/production

Link to debug log

Not relevant probably

@scottnonnenberg-signal
Copy link
Contributor

Thanks for the report! I've got a fix ready which moves our alt data to aria-label so the title is copied once more.

@protist
Copy link

protist commented Jul 15, 2018

I also saw this bug on Linux in 1.13.0. However, it looks like it's fixed for me by 1.14.1, which was released yesterday.

@mammuth
Copy link
Contributor Author

mammuth commented Jul 15, 2018

I still have the originally described behavior in v1.14.1-beta.1

@protist
Copy link

protist commented Jul 15, 2018

@mammuth Oh okay. I'm not sure what's going on then. Perhaps unrelated bugs, but that seems odd.

@scottnonnenberg-signal
Copy link
Contributor

It'll be in the next beta.

@mammuth
Copy link
Contributor Author

mammuth commented Jul 22, 2018

Fixed in v1.15.0-beta.5

@mammuth mammuth closed this as completed Jul 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants