Hi,When tokenising an end tag, the tokeniser switches to the Tag Name state (just like with a start tag). However, as a result, this now becomes syntactically valid:
</p foo="bar">There should be an easy parse error upon encountering the first non-whitespace character (except for '>') after the tag name, but which then continues to parse the attributes instead of just searching for the first occurrence of '>' because of the way browsers handle </p foo=">">
-- Lachlan Hunt http://lachy.id.au/
