You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have generated markdown and depending on whether I view it in the markdown-viewer or the MMDComposer5 the comments toward the end of the document in the various lists either displays as code blocks in the markdown-viewer, or don't display in MMDComposer5, respectively.
I believe the markdown-viewer plugin has become confused and introduced <pre><code> tags in the HTML it generates.
The purpose of these comments is to act as clues for LLMs to know where lists have been created and how they are indented.
Do you think this is a bug in the markdown-viewer?
I've attached a zip with the markdown and html used to produce it with the following content:
In the image below, the markdown we generated is on the left, the display in Chrome is in the middle, and the HTML that the markdown-viewer generated is on the right. Notice the introduction of <pre><code> tags added by the markdown-viewer:
wnm3
changed the title
Should HTML-style comments be displayed in code blocks?
markdown-viewer generates <pre><code> incorrectly from Markdown causing HTML-style comments to be displayed as though in code blocks
Jan 6, 2025
I have generated markdown and depending on whether I view it in the markdown-viewer or the MMDComposer5 the comments toward the end of the document in the various lists either displays as code blocks in the markdown-viewer, or don't display in MMDComposer5, respectively.
I believe the markdown-viewer plugin has become confused and introduced
<pre><code>
tags in the HTML it generates.The purpose of these comments is to act as clues for LLMs to know where lists have been created and how they are indented.
Do you think this is a bug in the markdown-viewer?
I've attached a zip with the markdown and html used to produce it with the following content:
codesmpl.zip
The text was updated successfully, but these errors were encountered: