Emoji text-mode modifiers are not supported

[n8willis]

If you type an emoji codepoint followed by the text-mode modifier (U+fe0e), then the codepoint should be rendered in text mode. Whalebird does not do this and, instead, renders the emoji in graphical mode.

How To Reproduce

1. Enter U+2695
2. Enter U+FE0E
3. View the results, which should show ⚕️︎ but instead show a full-color emoji: https://mastodon.social/@n8/103826808650315068

Your Environment

Linux; snap on Ubuntu

Note that I am observing this after #708 is fixed, and it does not involve the pop-up emoji picker.

[RuiNtD]

hmmmmm...

[n8willis]

What does that mean?

[RuiNtD]

That emoji shows up in my browser as a colored emoji as seen in the screenshot I posted before. Maybe it’s a Chrome / Electron bug?

[n8willis]

Try it in a terminal if you want to see the difference and be certain. We also cannot control what GitHub does to rendering Markdown content. If the GitHub site (or Chrome, if that's what you use to visit GitHub; I use Firefox) also mangles the modifiers, then that's a second and/or third bug for them.

Regardless, "U+2695,U+FE0E" should not be rendered identically to "U+2695" alone (as is also the case for dozens of other codepoints that were retroactively bound to emoji, of course). This happens while typing in the New Toot box in Whalebird, so it's not the Mastodon server stripping out the codepoint.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You can remove the stale label with /remove-stale comment. Thank you for your contributions.

[n8willis]

/remove-stale

[n8willis]

This needs to be re-opened; it still has not been fixed.

[stale[bot]]

/remove-stale

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You can remove the stale label with /remove-stale comment. Thank you for your contributions.

[n8willis]

This is still a bug and these auto-close-things bots are unethical, anti-community, and wrong.

[stale[bot]]

/remove-stale

[h3poteto]

Is anyone able to implement this? If not, I will close this issue because I will not do this.

[n8willis]

This is standard Unicode processing. Neither the application code nor the text-handling library should require any special treatment in segmenting or in interacting with the font.

https://www.unicode.org/reports/tr51/

If one or the other of them is mangling that Unicode control character, then the odds are it is mangling other things — at least in emoji sequences, and probably other shaping operations — as well.

[h3poteto]

I think this is the browser-side issue, I can't help it.

[n8willis]

There is no browser involved. The incorrect behavior reported here is occurring only within whalebird-desktop.

[n8willis]

There is no browser involved. The incorrect behavior reported here is occurring only within whalebird-desktop.

[h3poteto]

In the first place, I can't reproduce this. Even web UI, when I type U+FE0E

It is not rendered any emojis. https://mastodon-japan.net/@h3poteto/109703837384201451

I'm not sure how did you type the codepoint.

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity.

[n8willis]

I'm not sure how did you type the codepoint.

See https://help.ubuntu.com/community/GtkComposeTable , https://help.ubuntu.com/community/ComposeKey#Unicode_composition , or the like.