Batch Wizard - false validation errors

Post by **Albert Wiersch** » Mon May 19, 2008 12:57 pm

Strange... I did some tests with UTF-8 documents and could not reproduce this issue. I wonder if I had already done something that fixed this issue after releasing v8.9910. In any case, please try v8.9911 as soon as it is released (should be soon) and let me know if it fixes the problem. If not, then I'd like to get some more information about this problem.

Post by **Albert Wiersch** » Mon May 26, 2008 9:40 am

Albert Wiersch wrote:Strange... I did some tests with UTF-8 documents and could not reproduce this issue. I wonder if I had already done something that fixed this issue after releasing v8.9910. In any case, please try v8.9911 as soon as it is released (should be soon) and let me know if it fixes the problem. If not, then I'd like to get some more information about this problem.

Another person reported a similar issue and this time I had a URL to use to reproduce the problem so I was able to fix this in 8.9911. Thanks for the report.

Sares · Post by **Sares** » Tue May 27, 2008 12:56 pm

Hi Albert,

thanks for this information. I look forward to the next beta-release

Maybe I´ve found some other small bug(?).

If I validate this:

<img src="../../images/telephone.gif" alt="" width="13" height="9" border="0" />

I will get this warning:

Warning: [117] The value for the "width" attribute is "13" but the actual image width is "-1". The user agent/browser may resize the image but this may not be what is wanted. Usually the actual image width is used.

The images size is correct, 13 x 9, so I don´t now, could it be a bug??

Thanks for listening!
Sares

Post by **Albert Wiersch** » Tue May 27, 2008 3:58 pm

Sares wrote:The images size is correct, 13 x 9, so I don´t now, could it be a bug??

Thanks for listening!
Sares

This should already be fixed in the next BETA.

I had hoped to have BETA 1A out by now but ran into another issue.

Sares · Post by **Sares** » Tue May 27, 2008 4:11 pm

Thank you Albert.

I had hoped to have BETA 1A out by now but ran into another issue.

Don´t give up, you are doing a great job!

Sares

Post by **Albert Wiersch** » Wed May 28, 2008 12:31 pm

Sares wrote:Don´t give up, you are doing a great job!

Sares

Thanks! BETA 1A is out.

Post by **Albert Wiersch** » Wed Jun 04, 2008 5:43 pm

Sares wrote:Anyway, it would be fine, if the next beta will fix this problem, because it´s a bit annoying to have hundreds of errors in the validation report

Hello Sares,

Habe you tried the latest BETA 1C (v8.9913)? Please let me know if any problems remain.

Sares · Post by **Sares** » Thu Jun 05, 2008 12:59 am

Hi Albert,

the new beta works fine so far. No unexpected results in the validation output.

But I will make some additional tests using the batch-wizard and a large project and will report you if I run into problems.

Thanks,
Sares

Sares · Post by **Sares** » Thu Jun 05, 2008 1:21 am

Hi Albert,

back again with some new informations for you

Now I run the batch-wizard on a project with about 1000 Files and 99,2% are error free. So far so good. So let´s come to the error messages. All errors were found in .js - Javascript files, in libraries like prototype.js, scriptaculous.js and some others.

BUT - I have all Javascript validation disabled, the same with CSS validation, Search Engine Messages and Accessibility. And here comes the really strange part of the validation report.

ALL errors in the Javascript-Files are "Error (Parsing) [CSS]" messages. So it seems that HTML Validator validates my Javascript files which I have disabled and treat them as CSS files, which I also have disabled. So what do you think, strange, isn´t it??

I would be very happy if you could help me once again.

Kind regards,
Sares

Post by **Albert Wiersch** » Thu Jun 05, 2008 8:07 am

Thanks for the report. I'll be happy to help. It seems like CSE HTML Validator may think some JavaScript files are CSS. Can you send me some of the URLs or files that cause this problem? Or any sample document that I could use to reproduce the problem would really help.

Sares · Post by **Sares** » Thu Jun 05, 2008 8:26 am

Hi Albert,

the source is the same as published on page 1 of this thread.

But maybe a hint for you. In the summary batch-report HTML Validator says:

...

1. Documents that have errors

and then he shows all 8 Javascript files:

http://localhost/js/functions.js
http://localhost/js/dhtml.js
http://localhost/js/prototype.js
...

with thousands of errors. So it seems like CSE HV opens the JS Files as normal HTML Files and validated the source or something like that.

The functions.js File includes something like this:

Code: Select all

function swapImg(name,over)
{
    if(window.document.images) 
    {
        if (over)
            window.document.images[name].src = "images/" + name + "_over.png";
        else
            window.document.images[name].src =  "images/" + name + "_off.png";
    }
}

and I will get errors like this:

3:5 Error (Parsing) [CSS] Bad style format, cannot find the colon separating the style property from its value.
if(window.document.images)

3:5 Error (Parsing) [CSS] Cannot find an end brace for this style rule. A style declaration must be enclosed in braces, like in "h1 {color: red;}".
if(window.document.images)

5:9 Error (Parsing) [CSS] Bad style format, cannot find the colon separating the style property from its value.
if (over)

5:9 Error (Parsing) [CSS] Cannot find the selector for this declaration. A selector must precede a style declaration, like in "h1 {color: red;}". "h1" is the selector.
if (over)

10:1 Error (Parsing) [CSS] Found an extra right curly bracket. This right curly bracket should be removed.
}

--

So any idea??

Kind regards,
Sares

Post by **Albert Wiersch** » Thu Jun 05, 2008 8:44 am

Thanks. I think I know where the problem is and I plan to investigate it today.

Sares · Post by **Sares** » Thu Jun 05, 2008 8:51 am

Fine, thank you very much Albert.

If you need some additional information, please let me know.

All the best
Sares

Post by **Albert Wiersch** » Thu Jun 05, 2008 10:50 am

I believe I've fixed this for the next BETA. CSE HTML Validator was incorrectly thinking those JavaScript documents were CSS documents.

Sares · Post by **Sares** » Thu Jun 05, 2008 10:53 am

Great news, thank you very much Albert.

So I look forward to the next beta-release

Kind regards,
Sares