4 ms·
That was a good read. I reread the relevant section of the HTML5 spec and noticed an error in an example: > For example, ¬in will be parsed as "¬in" where
by masfuerte 1y ago
That was a good read. I reread the relevant section of the HTML5 spec and noticed an error in an example:
> For example, ¬in will be parsed as "¬in" whereas ¬in will be parsed as "∉".
Only a small minority of the named character references are permitted without a closing semicolon, and notin is not one of them. So ¬in is actually parsed as "¬in". ∉ is parsed as "∉".
https://html.spec.whatwg.org/#parse-error-missing-semicolon-after-character-reference https://html.spec.whatwg.org/#parse-error-missing-semicolon-...
- squeek502 1y agoGood catch, that does indeed look like a mistake in the spec. Everything past the first sentence of that error description is suspect, honestly (seems like it was naively adapted from the example in [1] but that example isn't relevant to the missing-semicolon-after-character-reference error). Will submit an issue/PR to correct it when I get a chance. [1] https://html.spec.whatwg.org/multipage/parsing.html#named-character-reference-state https://html.spec.whatwg.org/multipage/parsing.html#named-ch...