IE7, WaSP, ASP.NET and Standards


Paul Festa says it quote well in his article yesterday (http://news.com.com/A+standards+truce+in+the+browser+war/2100-1013_3-5818382.html)


I'm really excited about the work that is going on and the relationship that we have built with WaSP and the many thought leaders in the standards space.  It is personally inspiring to see the hard work that is going on within Microsoft to reach towards standards.  ASP.NET 2.0 and Visual Studio 2005 have been tracking well towards and standards and WaSP's support has really helped us focus in on the big wins -- here we have XHTML 1.0 Transitional support by default and Section 508/WCAG conformance out of the box, not to mention solid tools support to help developers validate their code against accessibility standards.  Further, IE7 is making great strides (which will be seen in Beta 2 and Chris Wilson details most of at: http://blogs.msdn.com/ie/archive/2005/07/29/445242.aspx


The future is bright, we are tracking to a positive trajectory and at the end of the day I think we are well positioned to add a ton of value for Web developers across our entire Web Platform and Tools stack. 


As always, I'm very open to your feedback, anything, anytime.


 


Comments (6)

  1. Mark Szentes says:

    What about ACID and ACID2? Safari and Konqueror pass them.

    http://www.webstandards.org/act/acid2/

  2. Jeff Parker says:

    You know I really like the fact your listening and working to make it right. I am so glad I will not have to do in 2.0 what I had to do in 1.1 and 1.0 which is rewrite every single webcontrol and make it compliant with even normal html and maybe I can use some of the other controls like the datagrid and so on(I just didn’t have the time to rewrite all those controls best not to use them if you cared about good html) Next thing you need to tackle now is Front Page. If front page is one of the primary editors for sharepoint sites for the users and front page can not create compliant html well then you will never have a compliant website in sharepoint.

  3. Mark, IE already passes the original Acid Test – it’s now part of the CSS1 Test Suite at the W3C. We’ve passed it for a long time now. See my post on the IE Blog about Acid 2.

  4. Brian,

    am I reading correctly between the lines that the target doctype for XHTML support in ASP.NET 2.0 has been changed from XHTML 1.1 to XHTML 1.0 Transitional?

    Nothing wrong with that in particular, just wondering. XHTML 1.1 seemed like a very ambitious target to me in the first place …

    Hardy

  5. bgold says:

    Hardy —

    Based on feedback we received from WaSP and the broader community it was felt that XHTML 1.1 Strict was the wrong way to go for default behavior and we were better off targeting XHTML 1.0 Transitional as our default. Of course, we still have XHTML 1.1 Strict validation, but by default the platform/tooling will target XHTML 1.0 Transitional now for RTM.

  6. Brianiac says:

    Special note to the VisualStudio Team, the IE team, and all web coders: Check the spec http://www.w3.org/TR/html4/struct/tables.html#edef-TABLE , the table tag does not contain tr tags, and hasn’t since 1999! Tables must contain tbody tags (and optionally thead and tfoot tags), and that’s where the tr tags go.

Skip to main content