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 22:46:27 -0400
To: "'Nikita The Spider'" <nikitathespider@gmail.com>
Cc: <www-validator@w3.org>
Message-ID: <000b01c6da03$7a839a80$6c29df45@mainbootdrive>

Philip--

My apologies.  I realized your probable reference after my reply.

First, this is not my code.  It is a remedy provided by Microsoft.  Whether
or not, the capability JavaScript value should be listed as "false", I have
no idea.  It works, works on multiple ASP.NET applications, resolves the
downlevel issue and was designed to exclusively specify the W3C Validation
engine user agent string.  

If you have first-hand knowledge that certain ASP.NET applications will not
be rendered appropriately for the W3C Validation agent and produce
validation errors without changing the value to 'false', please advise and
advise Microsoft.

Thanks.

C. Thacker


-----Original Message-----
From: Nikita The Spider [mailto:nikitathespider@gmail.com] 
Sent: Saturday, September 16, 2006 10:25 PM
To: craig@cprgltd.com
Cc: www-validator@w3.org
Subject: Re: Re: Re: asp.net panel browser inconsistencies

On 9/16/06, CPRG Limited <craig@cprgltd.com> wrote:
> Philip--
>
> This is not JavaScript.  It is a simple XML structured file that is 
> read by .NET Framework that identifies the W3C Validation engine so 
> that when .NET Framework renders the ASP.NET source code is not 
> downleveled and maintains the specified DTD Strict model.  This code 
> is never sent to a browser.  It gets rendered at the server by .NET.

Craig,
I realize that you don't know me, but please give me credit for being able
to recognize the difference between XML and Javascript! =)  I was referring
to this line in your XML:

<capability name="javascript"           value="true" />

I don't know ASP.Net but it sure looks to me like that line tells ASP.Net
that interpreting Javascript is a capability of the W3C Validator.


> -----Original Message-----
> From: Nikita The Spider [mailto:nikitathespider@gmail.com]
> Sent: Saturday, September 16, 2006 10:09 PM
> To: craig@cprgltd.com
> Cc: www-validator@w3.org
> Subject: Re: Re: Re: asp.net panel browser inconsistencies
>
> On 9/16/06, CPRG Limited <craig@cprgltd.com> wrote:
> >
> > <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>
>
> Hi Craig,
> The settings above might work for you, but FYI the W3C Validator 
> doesn't support Javascript. Very few (if any) non-browser user agents do
so.
>
>
> --
> Philip
> http://NikitaTheSpider.com/
> Whole-site HTML validation, link checking and more
>
>
Received on Sunday, 17 September 2006 02:46:35 GMT

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