[BUG] Placeholder/dummy html comments around examples break markdown processing · Issue #2379 · tabler/tabler · GitHub
More Web Proxy on the site http://driver.im/
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
#2362 was intended to cover a few extra cases where certain page headings were not being included in documentation tables of contents, and instead of adding new class names into the related filter script to match the headings, an attempt was made at a more generic or less brittle solution by wrapping examples in a 'dummy' html comment to indicate examples, eg: <!--EXAMPLE--> .
Unfortunately, it looks like something about the way that markdown blocks are parsed stops working when these comments are present, causing the HTML to not render correctly.
How to reproduce
Build and run a local copy of the documentation site using any commit based on or more recent than 7fc1d5c
@BG-Software-BG - Sorry for not catching this previously 😅
Maybe there's a way to solve it while keeping this idea of a dummy wrapper comment, but I'm not sure. Perhaps we just revert to 0c6b487?
Browser
N/A
OS
N/A
Screen size
N/A
Describe the bug
#2362 was intended to cover a few extra cases where certain page headings were not being included in documentation tables of contents, and instead of adding new class names into the related filter script to match the headings, an attempt was made at a more generic or less brittle solution by wrapping examples in a 'dummy' html comment to indicate examples, eg:
<!--EXAMPLE-->
.Unfortunately, it looks like something about the way that markdown blocks are parsed stops working when these comments are present, causing the HTML to not render correctly.
How to reproduce
## ...
into HTMLScreenshots
JSFiddle
No response
The text was updated successfully, but these errors were encountered: