On Tue, 10 Dec 2013, Boris Zbarsky wrote:
On 12/10/13 11:11 AM, Peter Cashin wrote:
Is the specification intended to have compliant HTML agents stop
parsing ambiguous ampersands?
Compliant HTML agents are allowed to do so, I guess, per the technical
rules about parse errors, just
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
On 12/10/13 11:11 AM, Peter Cashin wrote:
The HTML5 spec says that an ambiguous ampersand (e.g. something; undefined) is
not allowed in element content
Right, that's an authoring requirement.
and in section on HTML parsing, that this should throw a parse error.
There is no throwing of
2013-12-10 19:45, Boris Zbarsky wrote:
On 12/10/13 11:11 AM, Peter Cashin wrote:
The HTML5 spec says that an ambiguous ampersand (e.g. something;
undefined) is not allowed in element content
Right, that's an authoring requirement.
Authoring requirements as such are just policy statements,
On 12/10/13 2:33 PM, Jukka K. Korpela wrote:
Authoring requirements as such are just policy statements, therefore
regularly ignored.
In this case, it's an eminently validator-enforceable authoring requirement.
Allowing user agents to stop parsing after a parse error (BTW, where
exactly does
2013-12-10 22:20, Boris Zbarsky wrote:
In this case, it's an eminently validator-enforceable authoring
requirement.
That’s a more or less a wannabe-normative requirement that “validators”
are supposed to enforce. There is no real HTML5 validator so far (not
surprising, as there is no
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:
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
