Scott M. napisa³(a):
...And you point is? There's the W3C and then there is the real world,
happiness is somewhere in between.
this is poor excuse to not being able to generate clear, standard
compliant documents.
VS. NET still generates heaps and heaps of deprecated tags.
When you let vs.net do that it will be. But it's not reason to generate
tag soup and serve it to your users hoping they uses IE.
My asp.net apps (both 1.1 and 2.0) are valid xhtmls with tableless
layouts and fully separated content(xhtml), layout(css) and
behavior(js). And it was not big deal to achieve this. And they work in
most borwsers (that have js support. however it's achievable to make it
work without js too, but it involves much more work).
It's a fact that vs.net enables people with very low knowledge and
skills in web technologies to build "websites", but those "websites"
will be mostly very low quality and will work as author wants in IE only
and will have very messy html code - tag soup. Typical asp.net developer
has no background knowledge about web technologies basics (how http
works (get and post methods), how browsers renders documents, how
javascript works, even how asp.net works). Just look into many posts on
this newsgroup - they shows exactly what i said.
I know that asp.net allows me to work on higher level of abstraction,
and it's great. I can produce websites faster and with less coding. But
it all doesn't make me free to build poor coded websites and tell
everybody that's not my fault - asp.net does it.
Using asp.net is most effective when you know exactly what lies beneath,
and understand it's mechanisms that generates (x)html code. In this case
you can build standard compliant sites and don't have to make stupid
excuses about "milions of people that doing it that way".
It's like : Lets eat shit! Millions of flies can't be wrong!
Mark has noticed, that you show an example that uses deprecated
attribute and it was good. This is the right way to teach people how
they should build websites. IMHO there was no need to try to defend your
code.
But
that is perfectly ok because HTML or XHTML Transitional ARE standards.
Transitional specifications are standards, but it's not the same as "tag
soup" that is using strange tags combinations to achieve visual effects.
It's not about sets of allowed tags and attributes, it's rather about
how you use this tags and attributes and what for.
