Posted by Neo Geshel on 04/17/07 21:46

Neo Geshel wrote:
> • Validates as XHTML 1.1
> • Validates on all interior pages

Hmmm... it seems that having <xhtmlConformance mode="Strict" /> in the
web.config fails to throw ASP.NET 2.0 into standards compliance mode for
the W3C Validator. As such, when the Validator grabs the page, ASP.NET
2.0 will litter forms with name attributes and unencapsulated input
elements (check the source under Firefox... no name attributes or
unwrapped input elements!!). Great, just what I wanted. NOT.

So the W3C validator *will* complain on any page that has a form, but
Firefox gets kosher XHTML and so therefore will not throw a parser
error. Thank heavens for small miracles.

I will have to ask a MCSE MVP about this one. It’s clearly an ASP.NET
2.0 issue and how the script handles different clients. Problem is, this
host doesn’t allow me to access and recompile .browser files, so I can’t
exactly fix the problem by changing the server’s recognition of the W3C
Validator.

...Geshel
--
*********************************************************************
My return e-mail address is an automatically monitored spam honeypot.
Do not send e-mail there unless you wish to be reported as a spammer.
Please send all e-mail to my first name at my last name dot org, with
a subject-line of “NEWSGROUP REPLY FOR NEO GESHEL” (all uppercase).
*********************************************************************

[Back to original message]