[Webkit-unassigned] [Bug 14952] Unknown character reference (general reference) mistakenly treated as a fatal-error rather than a non-fatal error

[bugzilla-daemon at webkit.org]

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





------- Comment #7 from robburns1 at mac.com  2007-08-12 22:52 PDT -------
(In reply to comment #4)

Using the nightly build from totday 2007-08-13, the treatment of an unknown
character entity as a fatal error bug is confirmed. Just to reiterate, an
unknown character entity is not well-formedness constraint violation. It is an
invalidity constraint violation. It is therefore not a fatal-error and should
not be treated as a fatal error. Quoting this again:

"Conforming software may detect and report an error and may recover from it"
(http://www.w3.org/TR/xml/#dt-error). 

There is no requirement to even report this error ("may detect and report").
The Unicode replacement character should be sufficient notification to web
developers that there is a problem. I suspect this leniency is built into the
spec so that this type of draconian error-handling wouldn't show up in
implementations.

Just for contrast the fatal error norm states:

"Once a fatal error is detected, however, the processor must not continue
normal processing (i.e., it must not continue to pass character data and
information about the document's logical structure to the application in the
normal way)."

However, this is not a fatal error, except when processing a standalone='yes'
document.


-- 
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.