Just happened to notice some minor HTML errors in Google Blogoscoped as reported by the HTML Validator plug-in for Firefox – read more/download at:
https://addons.mozilla.org/firefox/249/
This is more a "plug" for that extension (which rocks – allows you to see at a glance how well your pages validate using the built-in Tidy validator) and *much* less a "you gotta validate Philipp" ... although since Philipp is usually so "with it" in standards, I was a bit surprised a few errors had creeped in.
Again, I'm not trying to sound overly picky toward Blogoscoped – just a very, very minor nit and passing on a tool I find that is very, very helpful. |
Actually, I only believe in the official W3C validator, as other validators are mostly non-conform. That being said, for the time the Ask campaign runs (till the end of this month presumably) this blog will indeed not validate! :)
But I gotta ask FM again, they told me they might be able to give me a JavaScript instead of an iframe. Iframes are not part of the Strict doctype. |
My experience is that Tidy does a prett decent job – I ran your main page and a seperate entry through the W3C validator (URL's below) and they reported similar warnings – does appear some of these are unrelated to the Ask ads (?)
Again, I am **NOT** try to nit-pick/whatever – just a casual observation I happened to notice. Heck, www.cnn.com is showing 247 warnings right now ... and www.google.com is 'famous' for not validating and having almost as many warning as words on their page. I'll take content over validation anytime and Blogoscoped offers tons of the former.
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fblog.outer-court.com%2F
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fblog.outer-court.com%2Farchive%2F2006-06-29-n69.html |
> does appear some of these are unrelated to the Ask ads (?)
Absolutely, I won't validate Google Blogoscoped till the end of this month, knowing that it will contain errors, so there's bound to be other errors piling up. I usually valiidate my blog about every week to fix the usual suspects, such as when I forgot to encode ampersands in URLs, or when I forgot to close a span element...
I'm also picky, that's why I like to have a valid blog. Again, this month is an expection. As soon as FM replies I might have a JavaScript ready to replace the Iframe :)
As for other tools being as good as W3C, it's certainly possible... |
.. and we're back to validating HTML :) |
HTML Validator shows 0 errors / 0 warnings on my end! |
