[Webkit-unassigned] [Bug 14945] An ampersand ("&") appearing in a document is treated as a fatal error (instead of a non-fatal error)

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=14945





------- Comment #11 from robburns1 at mac.com  2007-08-14 23:24 PDT -------
(In reply to comment #8)

OK, now I see what you're saying, Maciej. There are no (2) well-formedness
constraint violations nor any (3) parsed entity ill-formedness. However, the
document does not meet the (1) document production because  if you follow
through document production chain (http://www.w3.org/TR/xml/#sec-well-formed) 

document -> element -> STag -> Attribute -> AttValue

you'll find the following BNF notation:

[10]    AttValue           ::=          '"' ([^<&"] | Reference)* '"'
                                                |  "'" ([^<&'] | Reference)* "'

where the [^<&'] indicates the exclusion of '<', '&', and '"'.

Following the other chaing:
document -> element -> content -> CharData

reveals:

[14]    CharData           ::=          [^<&]* - ([^<&]* ']]>' [^<&]*)


excluding <', '&', and '"' from the element's content too.

This would override the earlier statement in the recommendation where the
inclusion of a '&' or '<' were only non-fatal errors. I'm satisfied this goes
against the recommendation. 

Dispatch this bug however you'd like.


-- 
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.