Problem with HTML validation errors

That was only 1 example, and a pretty basic one at that thinking about it. This happens literally hundreds of times throughout the site for various different reasons.

Here's another example (a better one):

            <SCRIPT language="javascript" type="text/javascript">
            if ((screen.width == 1024) && (screen.height == 768))
                     document.write("<td valign='top' height='560'>");
            else document.write("<td valign='top'>");
            </SCRIPT>

And another example:

<SCRIPT type="text/javascript" language="javascript">
if ((screen.width == 1024) && (screen.height == 768))
   document.write("<table width=180 border=0 cellspacing=2 cellpadding=1>");
else document.write("<table width=155 border=0 cellspacing=0 cellpadding=0>");  
</SCRIPT>

So in this last example, a validation error will occur because there will be a </TABLE> tag later on which won't be correct as it doesn't recognise that <TABLE> tag occurs earlier in the document.

Hope that makes my problem clearer. Thanks for your suggestion.

Cheers
SWD

Since the validation tool does not interpret JS, you're going about this a little wrong.

You should instead copy the source of the rendered page from your browser, and paste this into the validator. It is this source you want validated.

I see your point.

What I'm actually trying to do here is improve their google ranking, and I was told that fixing the errors would help (see http://www.experts-exchange.com/Web_Development/Internet_Marketing/Search_Engine_Optimization_SEO/Q_22468444.html).

I'd also like to be able to put a Valid HTML button on the site, but I can't do this if when people click on it they're taking to a page which tells them that are over 100 errors.

So what would you recommend that I do?

Thanks
SWD

Eventually, it becomes counterproductive to try and patch errors all day long.  At some point, it will be faster to rewrite the application.  I don't know how far you are in this process, but it's at least something to consider.

I'm kind of hoping someone will come up with a great solution for getting round this as once I have a solution for one of the errors I'll be able to implement it reasonably quickly for all of them.

I've wiped out pretty much all of the errors which are not caused by these suspect programming (the genuine errors so to speak) but I'd really like to have an error free site without having to rebuild the whole thing for them.

Thanks
SWD