Thank you for your time in completing this issue! 馃檶
What is your suggestion?
Not all cases of how an obsidian comment is explained.
Currently just like #1126 for block comments
x1%%x2
<insert-comments-here>
x3%%x4
its not clear what text (excluding composite syntax/ whitespace and >) can be inserted at all the xs.
its not a comment if x1 contains text which agrees with normal block syntax and the html comment <!-- -->
But unlike html comment, markdown in x4 is rendered as to html comments where its plain text.
For example
<!--
comment
--> _inline markdown_
gets rendered as
_inline markdown_
whereas it gets rendered as
inline markdown
for obsidian comments
Have any context we can refer to?
Thank you for your time in completing this issue! 馃檶
What is your suggestion?
Not all cases of how an obsidian comment is explained.
Currently just like #1126 for block comments
its not clear what text (excluding composite syntax/ whitespace and
>) can be inserted at all thexs.its not a comment if
x1contains text which agrees with normal block syntax and the html comment<!-- -->But unlike html comment, markdown in
x4is rendered as to html comments where its plain text.For example
gets rendered as
_inline markdown_whereas it gets rendered as
inline markdown
for obsidian comments
Have any context we can refer to?
still would say the docs are too unclear to decide if this behaviour is a bug or not.