What you are saying is correct when your code distort the right settings. It
appears from the original post that the validation errors are caused by
additional attributes that are likely needed for the client-side code. I
myself introduced such attributes several times in my code. If that is the
case, and you want to eliminate the validation errors, you would need to
modify the schema used for validation. This task may be far beyond your
capabilities and time/budget constraints and you would prefer rather live
with the errors.
--
Eliyahu Goldin,
Software Developer & Consultant
Microsoft MVP [ASP.NET]
"Przemek Ptasznik" <pp******@mila.wywal.to.edu.pllwrote in message
news:el**********@inews.gazeta.pl...
Eliyahu Goldin napisa³(a):
>First, you don't have to fix validation errors. They don't stop your
program from running correctly.
Partially true. Your webpages will work.
But it's good habit to validate your (x)html files. It's important to
produce standard compliant code because in this case you don't rely on
browsers "quirks" mode rendering. The less errors in validation result,
the less points where browser guessing "what you meant writing this piece
of code". Errorless code means easier way to make it work properly because
if something's wrong and your code validates - it's obvious that you
screwed and not the browser "AI":)
--
PP