You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some native OS emoji pickers (e.g. GNOME) explicitly add, after the inserted emoji, the "emoji presentation character" U+FE0F, which is an explicit request to present the previous character as an emoji instead of a text character - see https://www.unicode.org/reports/tr51/#Emoji_Variation_Sequences
The big emoji logic doesn't handle this character being present, so emoji sequences inserted this way end up small.
To reproduce
For each of the below emoji sequences, copy/paste into the message field and hit Enter. The first sequence has a U+FE0F between the first emoji and the space. The second doesn't.
😄️ 😄
😄 😄
Actual result
Small emoji.
Big emoji.
Expected result
Big emoji.
Big emoji.
The text was updated successfully, but these errors were encountered:
Although arguably an emoji picker adding the emoji presentation selector to a character with only an emoji presentation is pointless and likely to lead to bugs like the above, it makes sense to do so when the character has two possible presentations, so Element should handle this correctly.
I will file a bug with GNOME (actually GTK) separately about only using it when necessary.
Some native OS emoji pickers (e.g. GNOME) explicitly add, after the inserted emoji, the "emoji presentation character" U+FE0F, which is an explicit request to present the previous character as an emoji instead of a text character - see https://www.unicode.org/reports/tr51/#Emoji_Variation_Sequences
The big emoji logic doesn't handle this character being present, so emoji sequences inserted this way end up small.
To reproduce
For each of the below emoji sequences, copy/paste into the message field and hit Enter. The first sequence has a U+FE0F between the first emoji and the space. The second doesn't.
😄️ 😄
😄 😄
Actual result
Expected result
The text was updated successfully, but these errors were encountered: