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

breakage when trying to enter Unicode character using ctrl+shift+U just after emoji #7136

Open
2 tasks done
qcGVkzEG opened this issue Jan 19, 2025 · 1 comment
Open
2 tasks done

Comments

@qcGVkzEG
Copy link

Using a supported version?

  • I have searched searched open and closed issues for duplicates.
  • I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

On Linux (Wayland), trying to input a Unicode character between an emoji and some other character causes the UI to break. (See explanation and screenshots below.)

Steps to reproduce

  1. Compose a message which contains an emoji entered using the :something: shortcuts, and some more characters afterwards. (The bug does not occur for emoji that were entered directly as Unicode characters.)
    Image
  2. Move the cursor just behind the emoji and press ctrl+shift+U to enable Unicode input.
    Image
    At this point the rendering already starts to break (normally only the 'u' is supposed to be underlined):
    Image
  3. Try inputting a Unicode codepoint in hexadecimal. Normally, upon pressing the space bar, the "uXXXXX" sequence should be replaced by the corresponding Unicode character. Here, however, no replacement occurs:
    Image

Expected result

Inputting the Unicode character using ctrl+shift+U should work.

Actual result

See above in "steps to reproduce".

Screenshots

No response

Signal version

7.38.0

Operating system

Linux (Wayland)

Version of Signal on your phone

No response

Link to debug log

No response

@scottnonnenberg-signal
Copy link
Contributor

Ah, that's unexpected - sorry about that. Does that Ctrl+Shift+U shortcut work as the first thing you do in a text box? What might be happening is that the emoji is not considered text, so you're essentially in a new text box right after the emoji.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants