Aidan Woods

@fabiospampinato As you noted, the HTML block started by `` requires a blank line to end it, and HTML blocks are leaf blocks (cannot contain other blocks) so the line...

Would love to see a formal section on precedence rules for everything, even block interruption rules are quite spread out. E.g. With lists, the precedence rules that an [empty list...

The line: > If some lines in *Ls* are blank lines, then trailing whitespace after a block quote marker may be omitted without affecting the interpretation of which block quote...

@ScottAbbey how does that look?

> I think I don't really understand this new rule yet, but does it mean that (in the worst case) the whole block quote has to be parsed before it...

> In the actual spec, we could specify that `>•` is the "real" blockquote marker and if the space is missing, it is still treated as blockquote marker, but there...

IMO if `>` is to be considered an error, it should just fail. Having it be silently tolerated (resulting in indentation misalignment) is confusing. Having it fail outright makes it...

I think the only way to resolve this may be to try and gauge some consensus from the community. Couple points though: > > Having it fail outright makes it...

I like this idea, especially so since it addresses uniformity while not breaking the `>>> foo` case and consistent uses of the shorter marker. It's also a nice bonus not...

@fiveop that's a good point, perhaps "HTML element" wasn't the best choice there. For brevity, interpret the word **hyperlink** in the following to mean "link element of the document data...