W3C home > Mailing lists > Public > www-validator-cvs@w3.org > November 2012

[Bug 17418] & did not start a character reference and Errors involving fragile syntax constructs

From: <bugzilla@jessica.w3.org>
Date: Sun, 04 Nov 2012 10:23:38 +0000
To: www-validator-cvs@w3.org
Message-ID: <bug-17418-169-59HKhLxALt@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17418

--- Comment #6 from Michael[tm] Smith <mike@w3.org> ---
(In reply to comment #3)
> Tested with the attached test case. The error never showed up where it
> shouldn't. Tested it on other sites as well. Looks like the patch is working.
> 
> Based on http://www.w3.org/TR/html5/named-character-references.html, an
> error should have shown up for "&dollar" and "&minus", but the live
> validator (http://validator.w3.org) does not recognize them as named
> character references, so I imagine that is a separate bug.

The validator does recognize "&dollar;" and "&minus;" as valid named character
references. The current spec actually does not require it to recognize
semicolon-less "&dollar" and "&minus" as special in any way, and they are not
errors, so the per-spec behavior for them it to report nothing at all.

I realize that the validator (actually the HTML parser used by the validator)
does report "Named character reference was not terminated by a semicolon"
errors for semicolon-less versions of some named character references such as
"&reg;". I'd need to look at the code more to figure out why it does that for
some and not for others. I suspect it just has to do with length. But
regardless, the current spec doesn't actually define "&reg" as a parse error,
so I think the actual bug here might be that the parser is emitting any error
message at all for the "&reg" case.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 4 November 2012 10:23:40 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:17:53 UTC