[theme-reviewers] W3C Validator panel for Debug Bar
otto at ottodestruct.com
Thu Apr 26 21:52:10 UTC 2012
I gave up on the W3C Validator back when HTML 5 shifted from being a
draft to a "Working Draft" which means that it's live but will
continually get updated with new stuff. Basically, the validator can
no longer keep up with the standards being used, and so it doesn't
return particularly useful results.
It is still handy to use it to determine the more obvious errors and
such, but most of the results given tend to be of the ignorable kind,
where what is actually used in the real world isn't part of the
validator's code to check. It's not that the code is non-standard,
it's that the validator doesn't know that standard and so flags it.
So generally, use it as a tool, but don't aim for "100% valid" because
it's no longer realistically achievable.
On Thu, Apr 26, 2012 at 12:51 PM, Bruce Wampler <weavertheme at gmail.com> wrote:
> I am just curious as to appropriate use of the W3C Validator. How useful is
> it, really, at this point in time?
> For example, there a a number of HTML markup tags being generated by
> WordPress that will get flagged. For example:
> <time class="entry-date" datetime="2011-11-01T22:39:55+00:00" pubdate>
> [flags pubdate]
> <a href="http://weavertheme.com/category/news/" title="View all posts in
> News" rel="category tag"> [flags rel="category"]
> There are other rel tags that fail, too.
> And this is not to mention now commonly included og: meta tags for Facebook
> So how to use the tool? Is there a general list of acceptable errors? Does
> WP.org need to register some of the rel keysords at the Mirorformats wiki?
> Bruce Wampler
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
More information about the theme-reviewers