Suggestion: Check elment first, attribute second

The validator first checks attributes, then the element.  This means if I do something
like:

	<csobj w="208" h="77" t="Button">

I get a long series of complaints about each attribute ("w", "h", "t") before
I find that the validator actually does not understand the <csobj>.  An
improvement would be to check the element FIRST, and give just one error message.

I've had trouble getting web page authors to use the validator, because of issues
like this (spurious error messages -- especially because of valid Javascript).
A way to be less strict might improve usage.

		-Bryce

	
       Document type: HTML 4.01 Transitional 

       Line 47, column 30: 
         ...           <p><csobj w="208" h="77" t="Button" cl="images/New ...
       Error: there is no attribute "H" for this element (in this HTML version) (explanation...)

       Line 47, column 37: 
         ...         <p><csobj w="208" h="77" t="Button" cl="images/NewFi ...
       Error: there is no attribute "T" for this element (in this HTML version) (explanation...)

       Line 47, column 49: 
         ... csobj w="208" h="77" t="Button" cl="images/NewFiles/start_on ...
       Error: there is no attribute "CL" for this element (in this HTML version) (explanation...)

       Line 47, column 83: 
         ... " t="Button" cl="images/NewFiles/start_on.gif" ht="images/NewFiles/sta ...
       Error: there is no attribute "HT" for this element (in this HTML version) (explanation...)

       Line 47, column 114: 
         ... s/start_on.gif" ht="images/NewFiles/start_off.gif"><a href="index2.htm ...
       Error: element "CSOBJ" not defined in this HTML version (explanation...)

Received on Thursday, 2 August 2001 10:01:27 UTC