- Strict column-0 check: Under the CommonMark specification, fenced code blocks are valid with up to 3 leading spaces of indentation (
0–3 spaces). However, our markdown parser was previously expecting the backticks to be strictly at column 0 (no leading spaces). - Cascading fence mismatch: Because
`jshad a leading space, the parser treated it as regular paragraph text. When it hit the closingon line 10, it mistook it for the **opening** of a new code block. That block then swallowed everything below it—including the `theme-select.component.ts` link and thetsfence—until reaching the closing`at the end of the snippet.
Resolution
We have deployed a fix to both the server-side parser and the live editor preview:
- Fenced code blocks with 0 to 3 leading spaces are now fully supported according to the CommonMark specification.
- Indentation is stripped cleanly, and each code block is parsed and highlighted independently.
Your post now renders properly into two separate syntax-highlighted code blocks with the link displayed between them. Thank you for reporting this!