It's still draconian error handling, all the spec says is that you have to stop parsing and notify the user.

> Meh.

There were many circumstances that prevented the adoption of XHTML-as-XHTML. One of them was the fact that your users would get a cryptic error page, with no context, if something went wrong.

What Webkit does is much less threatening.