A
Alan Silver
Hello,
I am a complete and utter newbie at ASP.NET, so please forgive any
stupid questions ;-)
I am just trying to get my head around the whole web forms business, but
have run into a problem. I have been a web designer for many years and
have always made a specific point of writing HTML that is valid
according to W3C specifications. With web forms, the .NET framework
seems to generate some of the HTML, and what it generates is not valid.
For example, there is no attribute "name" in the HTML specs, but this is
generated for form elements. Also, the content of an "id" element cannot
start with an underscore according to the specs, but the hidden input
fields that it generates to keep state use just this.
It seems a shame that MS have put all this effort into (what looks like)
a very powerful framework, then ruined it by generating invalid HTML
that is likely to choke non-IE browsers. I hope I'm wrong here and
there's some way around this.
Looking forward to being corrected (nicely please !!)
I am a complete and utter newbie at ASP.NET, so please forgive any
stupid questions ;-)
I am just trying to get my head around the whole web forms business, but
have run into a problem. I have been a web designer for many years and
have always made a specific point of writing HTML that is valid
according to W3C specifications. With web forms, the .NET framework
seems to generate some of the HTML, and what it generates is not valid.
For example, there is no attribute "name" in the HTML specs, but this is
generated for form elements. Also, the content of an "id" element cannot
start with an underscore according to the specs, but the hidden input
fields that it generates to keep state use just this.
It seems a shame that MS have put all this effort into (what looks like)
a very powerful framework, then ruined it by generating invalid HTML
that is likely to choke non-IE browsers. I hope I'm wrong here and
there's some way around this.
Looking forward to being corrected (nicely please !!)