It would aid programmatic conversion of the spec, and confuse me when
reading the spec less thereby avoiding bugs like 25871, if these states
matched the model of the rest of the tokenizer.
Thus I propose the bogus comment state becomes:
Consume the next input character:
U+003E GREATER-THAN
In Blink's implementation, we actually use two additional tokenizer
states for CDATA:
CDATASectionRightSquareBracketState,
CDATASectionDoubleRightSquareBracketState,
Adam
On Sun, Jun 8, 2014 at 6:24 PM, Geoffrey Sneddon
foolist...@googlemail.com wrote:
It would aid programmatic conversion of
