-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Inconsistent Markdown Formatting in Custom Status Field #32544
Labels
Comments
Giridharan002
changed the title
Inconsistent Markdown Formatting in Custom Status Field
Bug:Inconsistent Markdown Formatting in Custom Status Field
Apr 4, 2024
Giridharan002
changed the title
Bug:Inconsistent Markdown Formatting in Custom Status Field
Inconsistent Markdown Formatting in Custom Status Field
Apr 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
Operating System
Operating System Version
Ubuntu 22.04.4
It happens on the web browser too?
Yes, it happens on the web browser too
Rocket.Chat Desktop App Version
3.19.14
Rocket.Chat Server Version
6.7.0-develop
Describe the bug
When attempting to set a Custom Status in the Rocket.Chat desktop app, I've encountered an issue with markdown formatting for bold and italic text. Traditionally, in message fields, wrapping a word in asterisks (*) makes it bold, and wrapping it in underscores (_) makes it italic. However, this expected behavior is not consistent when applying the same formats in the Custom Status field.
How to Reproduce
Open the Rocket.Chat desktop app.
Click on the profile Avatar at the top left corner
Click on the Custom Status field.
Attempt to format text as bold by wrapping it in asterisks (*) or as italic by wrapping it in underscores (_).
Describe your Expected behavior
Text that is wrapped in asterisks (*) should be displayed in bold
Text that is wrapped in underscores (_) should be displayed in italic.
Anything else
No response
Are you willing to submit a code contribution?
The text was updated successfully, but these errors were encountered: