I'm a very experienced programmer and application designer, but I'm new to DNN (using 4.01) and fairly new to ASP.Net.  I'm learning it while using VS 2005.

I noticed that some of the html that was being built has this header:

[!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"]

But VS 2005 is complaining that many of the actual pages in DNN do not conform to this standard.

For example, tags without ending / marks, such as [br] or [hr], tag attributes that have unquoted values, [img] tags without alt attributes, etc.  As a learning exercise, I went thru the source code to try to fix as many of these issues as I could. 

Assuming folks on the DNN team are interested in these changes, how do I go about joining the DNN effort and submitting the changed code? 

There are also a lot of deprecated attribute tags in the source.  Is there any interest in updating them to the newer standard, or do they need to be kept in place for legacy browsers?

Thanks in advance

This is an issue that I have run into recently when creating a pure CSS layout skin. You can read more about CSS in DNN at this forum thread: http://forums.asp.net/718428/ShowPost.aspx

Problems arose in that the current DOC type puts browsers into quirks mode. - In order to get Opera to display correctly I had to change the DOC type to put the browsers in Standard mode. - This then raises issues if you put any skins on your portal that are reliant on the quirks mode and it also causes problems with the SolPart menu - but I got around this by using a pure CSS menu.

It's an interesting topic - you even need to check the default skins as there are open tags, capitals, etc. within the Default DNN skins as well.

---

Lee Sykes - DNN Creative Magazine - 600+ Video Tutorials, Articles, Interviews - July Issue 58 out now!


Twitter: www.twitter.com/DNNCreative

I don't know if this helps; but I read the following at Microsoft:

If you submit an ASP.NET Web page to a validation service such as the W3C Markup Validation Service, ASP.NET might render a version of the page that does not conform to XHTML standards. This is because the validator service does not report itself as a browser type that ASP.NET recognizes, such as Internet Explorer or Mozilla. When ASP.NET cannot recognize the browser type, it defaults to rendering downlevel markup, which does not include XHTML-conformant elements and attributes, or features such as cascading style sheet styles.

You can configure your application to send the correct XHTML-conformant markup ....

read more at:

http://msdn2.microsoft.com/en-us/library(d=robot)/exc57y7e.aspx

Fitz