Actually, Tatham was kind of right in a way. It is possible to get ASP.NET to give you compliant code. However, compliance and web standards are *not* the same thing. Compliance is only part of web standards (and one of the smallest IMHO).
Take for example the Internet explorer blog on msdn.com <http://blogs.msdn.com/ie/>. The search form on the could be completely valid markup (it's actually not because the id names start with an underscore, but it could be). However, the code there is emphatically *not* standard. Essentially they are trying to make a link to something that a sumit input or button element should be doing. To cover up this unholy substitution, they use a bunch of javascript. Of course the form is completely broken to users without javascript. Alan Trick csslist wrote: > wasnt bashing m$ was saying a FACT, you shouldnt have to use a 3rd party > tool to get it right and your server-side lang shouldnt destroy your > markup without user error. > > see other reply, the guy was right!! It does obviously favors ie and > last i check ie and compliance werent on the same page............. > > whats next? You gunna say frontpage writes complient code (if you know > what you are doing) ;)~ > > > Tatham Oddie wrote: > > Not true – you just need to know how to use it properly instead of > Microsoft bashing. > > If you do want to use the built in controls and still get compliant > markup, I can provide you with a really simple article on how to do so. > > Thanks, > > Tatham Oddie > > ...... > ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
