W3C home > Mailing lists > Public > www-validator@w3.org > November 2009

Re: Markup Validator Lacking...

From: Wayne Smith <wayne.smith@csun.edu>
Date: Thu, 12 Nov 2009 10:38:48 -0800
Message-ID: <4AFC5638.40104@csun.edu>
To: "www-validator@w3.org" <www-validator@w3.org>
CC: gb2985@googlemail.com
Lee,

1.  I am not sure there is enough information in this email message to 
be helpful.

2.  If by "Firefoxs extension 'HTML Validator'" you are referring to the 
"Web Developer" add-in for Firefox, please know that the "Tools | 
Validate HTML" function in the add-in simply points to the existing W3C 
Validator.  There should, in principle, be no difference in validation 
results between these two use paths.

3.  If by "latest firefox for greatest accuracy" you mean that some 
browser functionality in Firefox differs from the canonical, explicit 
standard, please know that the function of the W3C Validator is not to 
check browsers, but rather to check instantiated files (or more 
specifically, files defined by a specific document type.)

4.  Please provide an public, working example (URI) of "...all of the 
errors that your validator misses" and the members of this list can 
comment further.

Best,

Wayne

Lee Shallis wrote:
> Your validator just doesn't behave strictly enough, find any error
> prone page and compare your validators results to that of Firefoxs
> extension "HTML Validator" (latest firefox for greatest accuracy) and
> you'll see all of the errors that your validator misses.
> 
Received on Thursday, 12 November 2009 18:39:26 GMT

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