W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2013

Re: [whatwg] Should ambiguous ampersand be a parse error?

From: Peter Cashin <cashin.peter@gmail.com>
Date: Tue, 10 Dec 2013 17:50:03 -0500
Message-Id: <8288D4C2-3A07-4228-A40B-7300D91C8A84@gmail.com>
To: whatwg@lists.whatwg.org
Boris Zbarsky & Jukka K. Korpela:

Thank you for you responses -- they are much appreciated.

Sorry I talked about "throwing" a parse error, the specification does not say anything like that. It is just that I had thought that a parse error should be quite a serious issue --  but it seems that is not necessarily the case. 

You have given me confidence that browsers will continue to parse an ambiguous ampersand as normal text that is parsed verbatim, despite the fact that the specification says this is a parse error.

Thanks again,
Received on Tuesday, 10 December 2013 22:50:32 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:14 UTC