W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2012

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

From: Henri Sivonen <hsivonen@iki.fi>
Date: Wed, 19 Sep 2012 17:01:32 +0300
Message-ID: <CAJQvAudOQL_GNMmEVGNyWh31cxTwcFWrAaNyM6kz4kD_Z8ff9g@mail.gmail.com>
To: WHAT Working Group <whatwg@whatwg.org>
On Fri, Sep 7, 2012 at 7:25 AM, Ian Hickson <ian@hixie.ch> wrote:
> Browsers are certainly allowed to report syntax errors in their consoles.
> Indeed I would encourage it.

Unlikely to happen. I already faced reviewer skepticism for making
Firefox whine to console about encoding errors. I silenced the most
common encoding error to get the patch landed. Fortunately the most
common error is also the least actionable one (encoding not declared
in a different-origin framed document—ad iframe in practice) so
silencing it isn’t crazy from the perspective of the utility of the

As Mike said, Firefox reports most (not all!) parse errors in View
Source, though.

Henri Sivonen
Received on Wednesday, 19 September 2012 14:02:03 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:45 UTC