Titus

> they might as just put those outside the HTML code elements. With the current state, you can mark certain parts of the code as important, or link them. With...

Bringing complete consistency is impossible: HTML in markdown is a black box. It “sniffs” things that look like XML and switches to a different state based on it starting with...

> The chance of impact to existing markdown documents is extremely low. As your babelmark example shows, commonmark conforming parsers treat `` as an autolink. Where `foo:` is the scheme,...

The `scheme` must be 2 or more characters! https://spec.commonmark.org/0.29/#scheme

I personally don’t prefer adding another list of supported values to CM, as it increases the minimum memory/size footprint of all conforming markdown parsers. For precedence between HTML or autolinks,...

@ioquatix Could you solve this by doing the inverse? Right now, you have XML embedded in Markdown. What if you have a proper XML document, parse it, and then treat...

I believe that this change is terrible for accessibility of millions of existing, accessible, blog posts and other markdown pages currently in the wild. It is very breaking and I...

> images would always have an alt that is deliberately added by the author. > alt="" has a very specific meaning as it marks as non-visual and signals that it...

> how people write markdown out in the real world Do you have examples of this? Concrete reasons to make this assertion? I wonder if the statement is correct. Of...

While I understand the inconsistency (it is indeed not documented in CM), does this result in an actual bug for you? For what it’s worth, the HTML spec does the...