W3C home > Mailing lists > Public > www-validator@w3.org > September 2006

Re: Re: Re: asp.net panel browser inconsistencies

From: CPRG Limited <craig@cprgltd.com>
Date: Sat, 16 Sep 2006 15:51:01 -0400
To: <www-validator@w3.org>
Cc: <peter.krantz@gmail.com>
Message-ID: <000601c6d9c9$716eab90$6c29df45@mainbootdrive>

Peter---

Thank you very much.  

As I received your e-Mail, I was implementing a fix as prescribed by
Microsoft.

There are a variety of methods that can be used to identify user-agent
strings within .NET Framework, one of which was the one you referenced in
your reply.

The easiest for me to use is mentioned by Microsoft in their developer
library,  http://msdn2.microsoft.com/en-us/library/exc57y7e.aspx.

To perform the one I used and have tested .. It works very smoothly, is to
create a file folder in the root directory of both the testing and
production servers.

Testing server = your local computer within IIS on your hard drive.
Production server = your hosting company server.

Create a folder titled, App_Browsers, within the root folder.

Create a text file, labeled [anything].browser.  In this case, I created a
file labeled, W3C.browser.   Use any text editor, Notepad, etc. to create
this file.

Add the following to the file:

<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 it and upload the entire folder to your production server.

By the way, I have used the Web Development extension for Firefox for quite
sometime and consider it an invaluable tool.  Thank you for that.

Final Note:  

This solution was not easy to uncover.  Albeit, the discussion of whether or
not Microsoft should conform more quickly to Standards compliance has merit
but they are working towards it.  It takes time to undo years of doing
something 'different'.

It may have merit if the Validation Service included a workaround for this
issue within their Help and FAQ section.

Again, Peter, thank you for your proactive response and help.  It should be
used as an example within this forum.

Sincerely,

C. Thacker
CPRG Limited
Received on Saturday, 16 September 2006 19:51:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:22 GMT