- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 16 Sep 2006 20:08:08 +0000
- To: www-validator-cvs@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3734 craig@cprgltd.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #1 from craig@cprgltd.com 2006-09-16 20:08 ------- After much research, this is not a bug on the part of the W3C Validation Service. ASP.NET and .NET Framework v2.0 and v3.0 RC1 does not include the Validation Service engine in their recognized browsers and the rendered code gets 'downleveled' when rendered. This produces the errors in code that is sent to the Validation Service engine thus causing the code not to validate. A workaround is presented in the Microsoft Developer's Library at: http://msdn2.microsoft.com/en-us/library/exc57y7e.aspx The workaround entails creating a folder labeled App_Browsers within the root directory and adding a simple text file labeled [anything].browser. I created a file and labeled it, W3C.browser. Within the text file, add the following: <browsers> <browser id="W3C_Validator" parentID="default"> <identification> <userAgent match="^W3C_Validator" /> </identification> <capabilities> <capability name="browser" value="W3C Validator" /> <capability name="ecmaScriptVersion" value="1.2" /> <capability name="javascript" value="true" /> <capability name="supportsCss" value="true" /> <capability name="tables" value="true" /> <capability name="tagWriter" value="System.Web.UI.HtmlTextWriter" /> <capability name="w3cdomversion" value="1.0" /> </capabilities> </browser> </browsers> Save the file and upload the folder and the file to the root directory of your production server/hosting company. It is hoped, that the Validation Service will consider adding this fix to their Help and FAQ section. Sincerely, C. Thacker CPRG Limited
Received on Saturday, 16 September 2006 20:08:15 UTC