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
Convert ASCII to Emoji preference does not appear to be honored. After disabling this preference, users still experience ASCII being converted to emojis automatically.
Steps to reproduce:
Disable 'Convert ASCII to Emoji' in My Account > Preferences > Messages
Send a message containing an ASCII emoticon (:) or The final score was 0:3)
Witness :) convert to 😃 and The final score was 0:3 convert to 'The final score was 😇'
Expected behavior:
When 'Convert ASCII to Emoji' is disabled, no ASCII should be converted to emojis.
Actual behavior:
ASCII characters are converted to emojis, despite the disabled setting.
Server Setup Information:
Version of Rocket.Chat Server: 5.0.0
Operating System: Rocky Linux 8.6
Deployment Method: docker
Number of Running Instances: 1
DB Replicaset Oplog: Enabled
NodeJS Version: 14.19.3
MongoDB Version: 4.4.15
Client Setup Information
Desktop App or Browser Version: Rocketchat Desktop Client 3.8.7 and Firefox 103.0
Operating System: Ubuntu 20.04
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered:
Same here. We have bots that send file paths and that's a total mess now.
Even simple backslashes just disappear: c:\temp\tempfile becomes "C😕temptempfile".
Is expect this to be fixed soon as it seems to be acknowledged by a dev now?
Description:
Convert ASCII to Emoji preference does not appear to be honored. After disabling this preference, users still experience ASCII being converted to emojis automatically.
Steps to reproduce:
:)
orThe final score was 0:3
):)
convert to 😃 andThe final score was 0:3
convert to 'The final score was 😇'Expected behavior:
When 'Convert ASCII to Emoji' is disabled, no ASCII should be converted to emojis.
Actual behavior:
ASCII characters are converted to emojis, despite the disabled setting.
Server Setup Information:
Client Setup Information
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered: