XHTML Traditional 1.0 in Alpha 3.0

re: XHTML Traditional 1.0 in Alpha 3.0

Jonathan — Tue, 07 Mar 2006 20:25:07 GMT

IE7 probably has probalye with IE7 scripts....
the scripts probably are not needed to be included in IE7 ( real ) and therefor e might be causing conflicts.

In general, the HTML that is good for firefox, should be good for IE

re: XHTML Traditional 1.0 in Alpha 3.0

Jonathan — Wed, 08 Mar 2006 02:52:37 GMT

I can add the filter for you in base page, so that all pages implement it, and we can make it a portal setting option, or an application level option. (probaly application level, as this could have performance implications when it's turned ono, better it's only on for debuging and testing, and getting W3C stamps - which is what the browser file is for ;-)).

re: XHTML Traditional 1.0 in Alpha 3.0

Jonathan — Wed, 08 Mar 2006 02:54:03 GMT

more interesting.... we can place it as an option on a per module basis.... with a default portal setting.... and a default application setting.... kind of like how web.config has hierarchies.

re: XHTML Traditional 1.0 in Alpha 3.0

Jonathan — Wed, 08 Mar 2006 03:00:00 GMT

anyway.... what those filters does, i think asp.net 2.0 does anyway with the setting in web.config

The default value for the xhtmlConformance element in web.config is Transitional, making your ASP .NET 2.0 apps XHTML compliant without having to try :)

but.... we can use mode="strict" to force even more :-)

re: XHTML Traditional 1.0 in Alpha 3.0

Yannick Smits — Wed, 15 Mar 2006 15:52:15 GMT

I think you mean:
XHTML Transitional not Traditional