-
Notifications
You must be signed in to change notification settings - Fork 11k
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
Inline code formatting not correct for multi-line code #9625
Comments
This seems to be still a open bug? Hm ;( |
Yeah, that bug is still open. Also the documentation is not correct as there is a white space in the code tag: https://rocket.chat/docs/contributing/documentation/markdown-styleguide/#md031---fenced-code-blocks-should-be-surrounded-by-blank-lines |
Is this really a nearly 5y old bug and still not fixed? Can we have an update? |
May be it was fixed fo sure from 4.1 up to 4.8.7. |
I signed up for a trial Rocket.Chat account, the dashboard shows it's running version 6.2.2. I can enter multi-line preformatted text in the chat box (the back-ticks have to be on separate lines): I can post multi-line preformatted text via incoming webhooks, in the Posting it in an attachment's Posting it in an attachment's field does not work – it seems to get displayed as inline code: |
Today we have separate options for single line and multiline code, I'll be closing this for now, thanks! |
@MartinSchoeler multiline code formatting is still broken in attachment field. Example webhook payload: Looks OK in the mobile app: Broken in the desktop app (all on the same line): |
Description:
If you select a text in the chat text area (where you write messages) and want to mark it as inline code, it is not taken into account, whether the text that is selected is single-line or multi-line. It only works as expected for single-line text.
Server Setup Information:
Version of Rocket.Chat Server: 0.61.0
Operating System: Oracle Linux 7
Deployment Method(snap/docker/tar/etc): tar
Number of Running Instances: 1
DB Replicaset Oplog: Disabled
Node Version: 8.9.4
Steps to Reproduce:
Expected behavior:
Text should be transformed to
Actual behavior:
Text is transformed to
Relevant logs:
The text was updated successfully, but these errors were encountered: