[whatwg] Should ambiguous ampersand be a parse error?

Boris Zbarsky bzbarsky at MIT.EDU
Tue Dec 10 14:32:14 PST 2013

On 12/10/13 4:41 PM, Jukka K. Korpela wrote:
>>> Allowing user agents to stop parsing after a parse error (BTW, where
>>> exactly does the WHATWG HTML Living Standard allow that?)
>> Did you try following the links in my mail?  Let me try again, but this
>> time do actually follow the link:
>> http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#parse-error
> “This section only applies to user agents, data mining tools, and
> conformance checkers.” So what about conformance of documents?

You asked where the standard says that a user agent can stop after a 
parse error.  That's the section linked above.

Conformance of documents is pretty simple: any document with a parse 
error is non-conformant last I checked, though exactly where it says 
that varies depending on the syntactic construct.

> If browsers are allowed to quit, or to proceed, then this is a very
> theoretic proposition.

Conformance of documents is always a "theoretic proposition" if all 
possible inputs have defined processing.


More information about the whatwg mailing list