Edit history

Earlier versions of Fluxer client emoji picker and short code autocomplete doesn't convert the shortcode to unicode when sending a message, newest first.

Current version | Edited by Rex
Changes
4. Check the API call that sent the message to the server and look at the payload/bodyRemoved: ### Environment (optional)Removed: Removed: _No response_Removed: ### Logs or screenshots (optional)[image](https://feedback.fluxer.com/p/397#f-389)Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.
Show

Fluxer client emoji picker and short code autocomplete doesn't convert the shortcode to unicode when sending a message

Summary

When sending a message if it contains a an emoji that has been inserted via the emoji picker or the emoji autocomplete, it would not get converted to a proper unicode emoji when sending the message. While not being a very big issue, it can be confusing for bots, as there is no way to tell if the user typed the shortcode intentionally while not meaning to send an emoji.

Steps to reproduce

  1. Open a fluxer client ( Reproducable both on desktop client as well as the official https://web.fluxer.app/ client )
  2. Open developer tools to inspect the network requests
  3. Send a message with an emoji via the emoji selector or by auto completing it. ( Not copy and pasting a unicode emoji directly )
  4. Check the API call that sent the message to the server and look at the payload/body

Logs or screenshots (optional)

image
Original by Rex
Show

Fluxer client emoji picker and short code autocomplete doesn't convert the shortcode to unicode when sending a message

Summary

When sending a message if it contains a an emoji that has been inserted via the emoji picker or the emoji autocomplete, it would not get converted to a proper unicode emoji when sending the message. While not being a very big issue, it can be confusing for bots, as there is no way to tell if the user typed the shortcode intentionally while not meaning to send an emoji.

Steps to reproduce

  1. Open a fluxer client ( Reproducable both on desktop client as well as the official https://web.fluxer.app/ client )
  2. Open developer tools to inspect the network requests
  3. Send a message with an emoji via the emoji selector or by auto completing it. ( Not copy and pasting a unicode emoji directly )
  4. Check the API call that sent the message to the server and look at the payload/body

Environment (optional)

No response

Logs or screenshots (optional)

image

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.