commonmark-spec

commonmark-spec copied to clipboard

Consider not adding empty alt tags to rendered images

13

Originally reported in https://github.com/markdown-it/markdown-it/issues/885 ## Setup 1. Create a reference to an image that does not exist: `` ## Problem Common Mark currently renders this image with an empty `alt`...

mjbvz

Consider ignoring HTML (inline) in `alt` on image

15

CommonMark prescribes that markdown is interpreted, but corresponding tags not output, in `alt` on ``: > ```markdown > ![foo *bar*] > > [foo *bar*]: train.jpg "train & tracks" > ```...

wooorm

(Intentional?) inconsistency between 4.6 block HTML and 6.6 raw HTML comments

5

The block HTML algorithm here allows ``, ``, etc, as comments. These comments are also fine by the HTML parser ([13.2.5.44, case for `U+002D`](https://html.spec.whatwg.org/multipage/parsing.html#comment-start-dash-state)). (note there are a couple of...

wooorm

* This limitation is not imposed by block comments * This limitation is not imposed by HTML * This limitation is not expected to be depended on by authors Closes...

wooorm

Leave the content of `<code>` and related HTML elements untouched by CommonMark parser

15

Hello, Recently I discovered that CommonMark allows Markdown parsing within `` blocks! So if user had something like `**bold**` in their markdown content (which is analogous to Markdown `` `**bold**`...

kaushalmodi

code block \w filename

3

hi 👋 today i saw another documentation today elsewhere and found this:  I struck me that many quite often want to present a code example and giving it an...

jimmywarting

Parse link references without knowledge of definitions

3

Heya, I would like to understand the rationale behind https://spec.commonmark.org/0.30/#example-568 ```markdown [foo][bar][baz] [baz]: /url ``` ```html [foo]bar ``` This enforces on both users and parsers that `[foo][bar][baz]` cannot be "understood"...

chrisjsewell

example 31 is misplaced and unexplained

4

In 0.30, examples 31-34 are introduced by: > Entity and numeric character references are recognized in any context besides code spans or code blocks, including URLs, link titles, and fenced...

rsc

Clarify title parsing of link reference definitions

5

The text for [link reference definitions](https://spec.commonmark.org/0.30/#link-reference-definition) is a bit hard to comprehend and a bit contradictory. See the discussion [here](https://talk.commonmark.org/t/optional-title-of-link-reference-definitions/4021).

dbuenzli

Clarify link label matching

1

In the 0.30 spec we have: > One label matches another just in case their normalized forms are equal. To normalize a label, strip off the opening and closing brackets,...

dbuenzli