xml:lang in the light of error frequencies

http://hsivonen.iki.fi/test/moz/analysis2.txt

> 05:52 < Hixie> hsivonen: re the errors, target=_blank will have to  
> be dealt
>                with, "The internal character encoding declaration  
> must be the
>                first child of the “head” element." might be  
> something we can
>                change if no non-ASCII bytes precede it, xml:lang  
> might need
>                some processing (maybe hardcode it to namespaced  
> processing?),
>                and there's a couple of html4-deprecated attributes  
> that are
>                still there (language="" on script, and name="" on <a>)
> 05:52 < Hixie> other than that, in the errors hitting 10% or more of  
> pages, i
>                think we're catching only things i think we want to  
> catch
> 05:53 < Hixie> i think language="" on script and name="" on <a> are  
> probably ok
>                to leave as errors, it's not like people can argue  
> that html4
>                didn't warn them
> 05:53 < Hixie> target=_blank is a known issue
> 05:53 < Hixie> xml:lang i'm sure is on my list, but it would be  
> useful to have
>                an e-mail pointing out how common the error is exactly

This is the email pointing out xml:lang.

 From the start of February to the middle of March, 15% of unique URLs  
checked as (X)HTML5 by Validator.nu had an erroneous xml:lang  
attribute in text/html. (Note that since the divisor contains the  
XHTML5 pages as well, the percentage for HTML5 must be even higher.)

As before, I think we should make zero-width image and iframe border  
conforming, HTML 4.01 Strict table attributes (except axis) conforming  
and make iframe width/height conforming.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/

Received on Sunday, 16 March 2008 15:19:57 UTC