On 2012-07-11 08:52, Jonathan M Davis wrote:
??? I guess that I wasn't clear. I mean that with HTML, it ignores errors. The
browser doesn't spit out errors. It just guesses at what you really meant and
displays that. It "fixes" the error for you, which is a horrible design IMHO.
Obviously, we're stuck with it for HTML, but it should not be replicated with
anything else.
This is in contrast to your example of outputting an error and continuing to
parse as best it can in order to provide more detail and more error messages
but _not_ ultimately considering the parsing successful. _That_ is useful.
HTML's behavior is not.
Ok, I see. It seems we're meaning the same thing.
--
/Jacob Carlborg
