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

View: New views
2 Messages — Rating Filter:   Alert me  

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

by olivier Thereaux :: Rate this Message:

| View Threaded | Show Only this Message


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

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
OpenJade-users mailing list
OpenJade-users@...
https://lists.sourceforge.net/lists/listinfo/openjade-users

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

by Cindy Sue Causey :: Rate this Message:

| View Threaded | Show Only this Message

On 7/1/08, olivier Thereaux <ot@...> wrote:

>
> 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?


Just wondering out loud if there might be some way that they can be
subdued the way warnings are for the CSS Validation Service..

If I'm understanding correctly where this lays, I've personally used
what otherwise may appear useless as tips to track down the occasional
extra elusive reported error in my own [coding]..

Cindy :)

- :: -
Celebrating Olmstead ♥ June 22, 1999

CindySueCausey.blogspot.com
www.ButterflyBytes.com
Georgia Voices That Count, 2005
Talking Rock, GA, USA
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
OpenJade-users mailing list
OpenJade-users@...
https://lists.sourceforge.net/lists/listinfo/openjade-users