I suddenly discovered something that I haven’t seen before. I was writing in a markdown document and came to the bottom of the window, I continued to write but DT didn’t show what I was writing and I can’t scroll the source view. Here I was playing with syntax highlighting (which I haven’t managed to get to work) but the same thing happens when I just type text. Here is how it looks:
I note you were puttig a fenced code block with python in the first line.
If you are hoping to use syntax highlighting, the correct form is language-python.
They’re all showing code fences with short forms of the language (i.e. ruby instead of language-ruby). I’d wager that these are some other places
I agree that prism.js uses language-xxxx, but that is not related to the MD renderer: it could simply prepend the language- to any xxxx it finds at the start of the code fence and pass the whole thing onto prism. I think that DT should follow the MD conventions here (see above for the Github and markdownguide links). Or it should be forgiving enough to add the language- prefix if it is missing.
After investigating a bit… You’re of course right in that prism uses class names with a leading lang- or language-. OTOH, the MD-to-HTML converter produces this
<code class="javascript">
from this
```javascript
If, instead it would convert this start of a code fence to <code class="language-javascript">
all would be easy-peasy. May be it’s possible to have the converter have a look at the string after the start of the code fence and adjust the class name accordingly? That would bring it more in line with the leading other MD converters, I think.