AKA Panama Jack wrote:Actually most of those errors aren't really errors.
You misspoke.
They are errors in compliance to the W3c standards.
They may not be errors you care about, agree with, or feel are worthwhile to fix, but they are errors in compliance to the W3c standard.
AKA Panama Jack wrote:W3C wants all tags and attributes to be lower case even though browsers are case-insensitive where tags and attributes are concerned.
Again, your phrasing is off. W3C doesn't "want" anything. The standard, for the specific type of html that the author chose as his doctype
requires lowercase tags.
He is in control. He can choose another doctype if he doesn't like case-sensitivity - like HTML transitional.
AKA Panama Jack wrote:So a line with <INPUT ... is throwing a validation error even though it really is correct syntax.
For the doctype the author chose, it is NOT correct syntax.
AKA Panama Jack wrote:Personally, I think requiring lower case for tags and attributes is being more than a little anal. It might have some relevance if an upper case version of INPUT performed different actions compared to a lower case version.
Argue with the standards body before the standards are released, or choose another doctype. However, please be accurate in your statements. The doctype chosen on the page
requires lowercase tags. $var chose that doctype - he is choosing to be that rigid. He can alternatively choose HTML transitional, which is very loose in what it will accept.
AKA Panama Jack wrote:Also, the W3C validator has problems with javascript inside the page being validated. It will throw errors on valid javascript when it SHOULD be either validating it correctly or bypassing everything inside <script></script> tags.
Sorry, here again, if it was a different doctype, I would agree. (Notably, it has the same problem on html-trans pages, and it shouldn't. Then it would be a valid argument). But in XHTML, the javascript should live outside the document - not inside.
AKA Panama Jack wrote:If you changed it as the validator indicates it will fail to work properly. If you strictly follow the advice the W3C validator gives then many times your page will not work right in any browser.
Or, if you clicked the explanation, it goes into detail to explain that it commonly runs into this situation with authors improperly embedding javascript in an XHTML page.
If you ignore the requirements of the DTD you choose, then many times, your page will not work right in any browser either.