I just noticed that answers (I don't know about the questions), that used triple backticks codes in the body, don't show up in the suggested-edits review queue on side-by-side mode. Instead it shows an empty code block. See the pictures below:
1 Answer
It is being rendered correctly. That code was previously being rendered as inline code because at the time it was posted we did not support triple backticks for a code block. Now that triple-backtick code blocks are supported, attempting to render it in the new Markdown engine produces an empty code block, because all of the text is on the first line of the backticks. Any text on the first line of backticks is interpreted as language hinting and is stripped from the output.
You can copy-paste that block of Markdown into any editor on the network, and it will continue producing an empty code block. It needs an additional line break after the first three backticks to be rendered correctly using that format.
-
no, but did you open the answer out of the edit review? it was showing up there normally. you mean if we tried to edit that answer, then in the editor window (now, after supporting triple backticks) those line will not appear but that answer because was old and that is why it was visible?– αғsнιηCommented May 15, 2021 at 19:22
-
2The live rendering of a post is cached. It was still being displayed as inline code because it had never been re-rendered. You can also see it rendered incorrectly from the revision history, which doesn't use cached versions of the post: unix.stackexchange.com/posts/475756/revisions Commented May 15, 2021 at 19:23
-
@αғsнιη Markdown help for info string. When editing 1 or more backticks may appear the same, but doesn't produce the same result - think of one view as raw (or unrendered) and the other as rendered.– RobCommented May 15, 2021 at 19:41