[whatwg] Wasn't there going to be a strict spec?

Michael[tm] Smith mike at w3.org
Thu Sep 6 21:55:25 PDT 2012

Ian Hickson <ian at hixie.ch>, 2012-09-07 04:25 +0000:

> On Fri, 10 Aug 2012, Erik Reppen wrote:
> > Why can't we set stricter rules that cause rendering to cease or at least a
> > non-interpreter-halting error to be thrown by browsers when the HTML is
> > broken from a nesting/XML-strict-tag-closing perspective if we want?
> Browsers are certainly allowed to report syntax errors in their consoles. 
> Indeed I would encourage it.

Firefox's "View source" does it. It highlights syntax errors in red (that
is, things the HTML spec defines as syntax errors for text/html documents),
and if you hover over them, shows the text of the error message.


P.S. to Eric, if by "XML-strict-tag-closing" you mean having a browser
report XML well-formedness errors when it's parsing a document served as
text/html, I don't think you're going to get that.  Lack of
"XML-strict-tag-closing" in an HTML document doesn't make it broken. If you
want to catch XML well-formedness errors, I guess you'd need check by
running stuff through an XML parser separately. Also, I don't what you mean
by "broken from a nesting perspective"...

Michael[tm] Smith http://people.w3.org/mike

More information about the whatwg mailing list