This post demonstrates the bug. When a bit of text is <!-- commented out -->, Lemmy shows it anyway.
Is that valid markdown? Looks like html to me.
Some sites like Github also support a subset of HTML in their markdown parser, but I dont think that is part of markdown itself.
It looks like the markdown parser markdown-it does support html if I turn it on, would that be a security risk of any kind?
No idea, but I dont think there is any reason why we need to support html formatting.
Yeah. I’d rather us add manual extensions like the spoiler thing, than allowing html.
spoiler
this is a spoiler here
It’s useful to be able to comment out text when working on the kind of article that’s an ongoing work of research. Sometimes a bit of text is not ready for presentation yet, or there may be sources that muddy the article and should be concealed but preserved. Sometimes a source article is useful for the author to refer to, but the source is a paywall (like the Wall Street Journal) or it’s a CloudFlare site, both of which are unfit to show the public. I don’t even like to send people to sites that are Amazon-hosted. So in all of these cases, it’s useful to comment out the source until a replacement source is found.
Aside from comments, I recall running into a limitation with markdown tables. Consider the case where you have a cell in a table containing a multirow monospaced font object (to convey terminal output, for example). The markdown language supports it, technically, but markdown interpreters often screw it up. I’ve not tested that specifically on Lemmy, but the fix is usually to do an HTML table and then use markdown in the cells to get it into monospaced text spanning multiple lines within a row.
Here’s what happens when I try to put a spoiler in a table using pure markdown:
col 1 col 2 row with a spoiler :::spoiler spoiler this is a spoiler here :::
