Closed tallesl closed 9 years ago
Agree, +1. As I understand it, markdown should ignore everything within tags. I implemented this by rendering out the raw code and swapping out HTML elements ahead of markdown's toHTML call.
it seems to me that html in markdown should not be escaped.
:+1: This surprised me, and contradicted the behavior of other very compliant markdown parsers.
+1, this is not standard in any Markdown implementation I know of...
At the very least, it'd be enough to allow for inline HTML by explicitly disabling escaping at will.
:+1: Let's have a comment from a maintainer...
I'll be unsubscribing from this now, because I found the module marked to meet this requirement for me.
For me too the escaping of HTML is a bummer, but this is a duplicate of the open https://github.com/evilstreak/markdown-js/issues/16 and can thus be closed.
also using marked now.
I am also using marked
now, since it automatically escapes HTML inside Markdown.
Why?
Shouldn't markdown leave those alone?
Both Gruber's and Common Mark implementations seems to leave it alone.
I'm using some HTML content in my markdown files, this behavior is preventing me to use this module.