No XHTML 1.0 Strict in ASP.NET 2.0
The improved support for web standards in Internet Explorer 7 and ASP.NET 2.0 could make you believe that the people at Microsoft are finally catching up with the rest of the web. But are they really? They sure don’t seem to know the difference between XHTML 1.0 and 1.1, and they seem to think that Transitional DOCTYPEs are the default.
In ASP.NET and XHTML, Milan Negovan notes that the XHTML 1.0 Strict DOCTYPE is missing from Visual Studio 2005. Very odd, and very unfortunate. Milan has more to say about the DOCTYPEs that are available in Visual Studio 2005 in That Pesky Document Schema Picker: Part II.
I guess this means that we will continue to see clueless ASP.NET developers produce sites with an XHTML 1.1 DOCTYPE and a mix of HTML 4.01 and XHTML 1.0 markup. Transitional, of course.
Update: Ok, I obviously touched a nerve there. Sorry, I did not mean this as a flamebait, and I should have made it clear right from the title of this post that this isn’t really about ASP.NET. It’s about Visual Studio.
Visual Studio does not equal ASP.NET. I know that. You know that. And yes, it is possible to create your own controls that output perfectly valid and accessible HTML. But how many developers do that? Very few. That’s why improving the default is important.