jmdyck

In the paragraph that begins "Here is an example of color space conversion", the status quo: `...

> Arguably that's a bug in the status quo since you're supposed to only wrap on where whitespace would "naturally" occur. Would you prefer a separate PR to fix such...

> As far as I can tell we only have one instance. There's only one instance of 'newline after equals', yes, but there's more than one instance of 'newline where...

In this PR, there are many cases where, if the first non-blank on a line is an element, it isn't joined up with the previous line, but presumably should be....

- A lot of the `` tags are preceded by 2-10 spaces, where it should presumably be only 1. - Sometimes a `` isn't joined to the previous line (e.g....

I'm puzzled about the semantics of `data-noreformat`. E.g., in `source` at line 2449 (under "terms defined in URL"), there's a `` marked `data-noreformat`, so I expected that the whole of...

There are some spots where the reformatter has incorrectly dropped a space before a start-tag, e.g. - line 1324: `sets ofplugins` - line 6292: `Thelazy load scroll margin` - line...

There are some spots where the reformatter leaves an end-tag on a line by itself, where it should probably append it to the previous line, e.g.: - `` on lines...

> Yes, comments that are preceded with a newline and followed by a newline are considered structural and left alone (including internal linebreaks). Other comments are reflowed inline. Thanks. In...

I'm still puzzled about the semantics of `data-noreformat` (see https://github.com/whatwg/html/pull/11640#issuecomment-3367726885). --- At line 65870 of `source`, there's: ``` The requirement that data blocks must be denoted using a valid MIME...