Titus

### Subject of the feature Rest of unified uses lowercase, suffixless values. `RootNode` -> `root`. Would make sense to align them. ### Actual behaviour `ParagraphNode` ### Expected behaviour `paragraph` ###...

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" > ```...

(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...

* 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...

Remove restriction of balanced parens in definition destination

2

For links, balanced parens are useful: `[a](b(c))`, although it imposes a potential performance problem due to having to track that balance (*Implementations may impose limits on parentheses nesting to avoid...

#### Proposal The spec has [this to say on shortcut references](https://spec.commonmark.org/0.29/#shortcut-reference-link): > A **shortcut reference** link consists of a link label that matches a link reference definition elsewhere in the...

Mention that link reference definitions are constructed from paragraphs

9

### Problem According to the spec text: ```markdown [ ␠␠␠␠# a ␠␠␠␠b ␠␠␠␠]: ␠␠␠␠example.com ' ␠␠␠␠line1 ␠␠␠␠... ␠␠␠␠' ``` ...is fine: it’s a proper link reference definition. This lead me...

Character references in link definition labels

5

- Character references are allowed everywhere, except in fenced code, indented code, or code spans - They represent their resolved character, not syntax There’s even [example 318](https://spec.commonmark.org/0.29/#example-318) of having them...

Reword “entities” to “named character references”

1

The HTML spec (no longer?) does not reference “entities”. Instead, there are two/three types of character references: named, numerical (hexadecimal or decimal). (for reference: ) I think rewording the CM...

“Invalid Unicode code points” in numeric character references

4

[Decimal numeric character references](https://spec.commonmark.org/0.29/#decimal-numeric-character) references “Invalid Unicode code points”, but nowhere is it defined what those are. Hexadecimal numeric character references do not mention this limitation, but I guess imply...