Visit
http://validator.w3.org/file-upload.html and try to validate the
markup from any one of your asp.net pages to xhtml 1.0 ( strict or
transitional ). Matter in fact, I bet you'd have a very tough time even
getting one to validate properly to HTML 4.01 Strict.
Do I need to enumerate shortcomings for you? Apparently so. Please educate
yourself before asking such questions.
- Hidden inputs are not valid as a direct child of a form tag. They must be
contained w/in another containing element (div, span, etc).
- <script> tags must contain a type attribute ( type="text/javascript").
The <script> tags that asp.net generates do not contain this attribute.
- id attributes on elements cannot begin with underscores ( as in
__EVENTTARGET, __EVENTARGUMENT, __VIEWSTATE ).
- name is not a valid attribute ( as in the name attribute written to the
main form. this also invalidates the non DOM javascript that asp.net
generates.
- script must be contained w/ in a CDATA section
- <img runat="server" tags will automatically add a "border" attribute which
is not valid.
- ...
It's much more difficult for me as a developer to difficult for me as a
developer to write a filter to make all the necessary changes to the output,
input then it is for MS to simply modify the asp.net engine to render valid
markup for the developers chosen schema.
"Alvin Bruney" <vapordan_spam_me_not@hotmail_no_spamhotmail.com > wrote in
message news:um**************@TK2MSFTNGP10.phx.gbl...
And you are worried that microsoft has dropped the ball on XHTML
because...?