W3C home > Mailing lists > Public > www-validator@w3.org > July 2008

Re: [VE][76] This message is preceded by nine useless messages

From: olivier Thereaux <ot@w3.org>
Date: Tue, 1 Jul 2008 10:14:40 -0400
To: "R.W. Crowl" <silvermaplesoft@earthlink.net>, openjade-users@lists.sourceforge.net
Message-Id: <D51C260B-CB9E-4D72-9748-C99225FA8B45@w3.org>
Cc: W3C Validator Community <www-validator@w3.org>


On 1-Jul-08, at 12:46 AM, R.W. Crowl wrote:

>
>> Validating http://www.jtbusa.com/en/default.asp
>> Error [76]: "element X undefined"
>
> My problem is not with this error message; it seems to be adequate  
> to the task.
>
> Rather my problem is with the wasted effort and information with the  
> preceding nine error messages that provide no actionable information  
> because the problem lies with the element reported in this message.  
> Of course there's no attribute X for an element that doesn't exist!  
> Don't waste my time.

This is indeed a usability issue, that comes from the underlying  
parser, opensp.

I would love an option to filter out unknown attribute errors for an  
unknown element. I'd make it a default, actually: if <foo> is unknown,  
then of course for <foo bar="quz" ...> bar will be an unknown  
attribute and quz an illegal attribute value - but it's useless info.

Openjade folks, is this something that has been considered before?  
Would it be hard to implement?

-- 
olivier
Received on Tuesday, 1 July 2008 14:15:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:30 GMT