Recently I experienced a high profile site throwing some errors in Firefox, and their support rep suggesting me to use Chrome (of course I didn't). This brought the memories of "best viewed in IE" times...
But that isn't the primary problem. The primary problem is that its simply too hard for most web developers to install/run a HTML validator in their web browser and fix the errors it finds.
Try it out, run html validator, for a few months while browsing the public web, its almost a surprise when a major web site actually has syntactically correct code. As a "systems" programmer spending about 30% of my time doing web development, simply having my code syntax checked (yah I run php and javascript validators in my deployment package too) before it makes to the the browser increases my productivity significantly. In the year or so after I started running validators/JSlint/etc (1) a lot of things started making sense in HTML/CSS and I went from a crappy web hack, to being the guy in the office helping the full time web guys when they get stuck...
Now if I could just find a good way to ask "experienced" web developers if they run a validator without leading them to the "right" answer I might have a good interview question.
(1) Part of this was I completely customized our "build" environment so that there was a debug vs release package/deploy process too. Things like JS minificantion/php obfuscation only happen during release deployment. JQuery/etc are actually checked into the version control in their unminified version. Plus, it usually only takes one or two calls from a web developer who can't figure out why their code won't deploy before they start checking the build logs.
Best viewed with Netscape 3.0+ or Internet Explorer 4.0+.
©1996-2002 Chelsea Networks