Eric Jansson

Anyone who has ever tested dynamically generated Web application interfaces against HTML standards knows how time-consuming and boring it can be to do this manually. Commonly, Web designers and testers will use an online validator like the W3C HTML validator at http://validator.w3.org/, which takes the URL of an HTML file, or the uploaded HTML file itself, as its input, and returns a report of any markup issues. The problem - and what makes the process time-consuming - lies in submitting these HTML files to the validator. Source code that generates HTML - a stew of HTML, scripting tags, and code blocks - won't validate by itself. We can, of course, remove the scripting tags and other code to validate the "raw" HTML in the file before any dynamic content is added at runtime, but this misses the point. We want to validate the whole enchilada - both the HTML markup in ... (more)