Markdown Incorrect Colorization of Fenced Code Blocks Inside of Block Quotes

[mjbvz]

For a markdown file like this:

> ```js
> 
> ```

**Blue Bold** white

The colorization is incorrect. Depending on what language is targeted, the colorization can break out of the code block entirely:

Here's what things should look like:

The problem is that that block quote opening > are included as part of the fenced code block content. This causes some language colorizers to freak-out and highlight the entire rest of the file.

[ghost]

I suppose that this issue is kind of related to #3746. I'm having the same problem right now with JS code blocks.

[mjbvz]

@dcbrwn Yes, this is another manifestation of #3746 but triggered by different behavior

In markdown, the fenced code block tokenizers for various programming languages can currently escape outside of the fenced code block if there is a syntax error in the block. In this example, the > is included inside the code content of the fenced code block because of incorrect parsing of block quotes. The Javascript highlighter sees the > and breaks out of the block entirely, and then tries to highlight the rest of the file.

I'm planning to address the core problem of fenced code block breakout soon.

[ghost]

@mjbvz, mine issue with JS, TS and alike is caused by template string quote introduced in es6 ("`"). Workaround for now is to stick code blocks to some text like this (added back-slashes to preserve "```"):

Some text example:
\```typescript
const a = `the ${template} string`;
\```

[mjbvz]

Original issue fixed by #14626

@dcbrwn I think the issue you identified has also been fixed:

Please try out the latest insiders builds and let me know if this is not the case.

[calebmer]

Thanks so much guys for all the great work you do 🎉

[ghost]

Seem to work as expected 👍