[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 bugzilla-daemon at webkit.org
Tue Aug 14 20:14:49 PDT 2007


------- Comment #10 from robburns1 at mac.com  2007-08-14 20:14 PDT -------
There is a trade-off between this bug and the other one I filed: bug#14952. If
the parser is going to try to handle unknown references then once an & enters
the parser it needs to treat it as a potential character reference. Once the
parser reaches a semi-colon it can close the character reference (known or
unknown). If it reaches another &, ', ", closing-tag, opening-tag or EOF, then
there is some flexibility on how it treats the string from the initial
ampersand and this point. It can either decide to close the character reference
at that point (and pass it to determine if its a known or unknown character
reference), or it can treat it as a misused & with no character reference at

After passing the string to a processor to determine whether the string
represents a known character reference, that step could either replace the
string with: 

1) a character referenced by the character reference
2) the Unicode replacement character
3)a more glaring markup that really draws attention to the error (if it occurs
in an attribute value, the markup could replace the entire element or the start
of the element)
4) the literal string passed on unchanged (with now a literal & as if it were a
& followed by the remainder of the string)

There's no reason to treat this as a fatal-error whatsoever.

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.

More information about the webkit-unassigned mailing list