W3C home > Mailing lists > Public > public-html-xml@w3.org > January 2011

Reporting errors (was: Re: Use cases)

From: Henri Sivonen <hsivonen@iki.fi>
Date: Thu, 6 Jan 2011 16:16:49 +0200
Message-Id: <AEAF6281-20C3-4F54-B514-4CC1A8F20F8D@iki.fi>
To: public-html-xml@w3.org
On Jan 5, 2011, at 17:08, David Carlisle wrote:

> No one (I think) is going to suggest that you get errors from the html parser, so the other choice (other than just accepting the data corruption and documenting how to avoid it) is to make the result of parsing less corrupt.

Although I'm not suggesting exposing parse errors in the CSS view port, the following are within the realm of semi-planned possibility for Firefox:
 1) Reporting bogus use of /> to the Error Console.
 2) Highlighting most Parse Errors (excluding Unicode layer errors and excluding validation errors) in View Source. Note that Firefox already highlights bogus use of /> in View Source.
 3) Reporting most Parse Errors to the Web Console if the Web Console is open during document load.

(This is not a promise to implement any of the above.)

Henri Sivonen
Received on Thursday, 6 January 2011 14:17:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:58:27 UTC