For a long time I've been the kind of web developer that enjoys
writing clean, valid code. I have some web friends that think I'm a
little too hard core, but it makes me happy. When I complete a site (or
when I run into a problem while developing the XHTML/CSS), I
use the Web Developer's Toolbar in Firefox to quickly run the page
through HTML and CSS validation. No, I don't put the little button on
my sites — who really cares? But I do make sure it validates.
week, I had a really odd phenomenon happen. I found myself using
proprietary CSS, causing my page not to validate, and then told
someone, “Who cares if it validates!” Shocking coming from my mouth… or fingers.
That said, what's validation really for? Is it the end, or the means
to an end? Is the goal to create pages that work in the validator? Or
pages that work in all major browsers and sell whatever your client is
I've come to believe that if I have to use proprietary code to force a certain browser which shall remain nameless
to render code the way it would be rendered if that browser were
standards-compliant, and it doesn't harm any other browser's rendering
of the page, then I've done my job. If rest of the CSS validates and is
written correctly, then I've used my tools wisely and created a site my
client can make money from and I can be proud of.