[whatwg] Should ambiguous ampersand be a parse error?

• From: Peter Cashin <cashin.peter@gmail.com>
• Date: Tue, 10 Dec 2013 11:11:06 -0500
• To: whatwg@whatwg.org
• Message-Id: <49FDCA6B-E22B-40B8-BECB-0693073E2FE8@gmail.com>

HTML5 authors:

The HTML5 spec says that an ambiguous ampersand (e.g. &something; undefined) is not allowed in element content, and in section on HTML parsing, that this should throw a parse error. 

However, browsers seem to render an ambiguous ampersand verbatim, which appear to be a good thing to do.

Is the specification intended to have compliant HTML agents stop parsing ambiguous ampersands?

I suggest it would be better to amend the specification to say that HTML5 agents "should" accept an ambiguous ampersand and render the text verbatim (as plain text characters), rather than throwing a parse error.

Is there a historic or technical reason for the specification wanting to treat an ambiguous ampersand as a parse error?

Peter.

Received on Tuesday, 10 December 2013 16:11:38 UTC