Invalid char index error

[Baretull]

Hi just downloaded the BETA 2 and tested it with some UTF-8 documents. Half of them seem to process fine, and half halt on a verification error:

Invalid char index for insert: 13930. Valid range: [0, 13915].

Invalid char index for insert: 9047. Valid range: [0, 9030].

Invalid char index for insert: 12419. Valid range: [0, 12396].

Invalid char index for insert: 12558. Valid range: [0, 12538].

Invalid char index for insert: 13381. Valid range: [0, 13362].

Invalid char index for insert: 15499. Valid range: [0, 15482].

Invalid char index for insert: 21418. Valid range: [0, 21414].

Invalid char index for insert: 11496. Valid range: [0, 11480].

[Albert Wiersch]

Hello,

Can you send me the steps to reproduce this problem and any needed files to support at htmlvalidator dot com? Thank you.

[Baretull]

The files are in the mail...

[Albert Wiersch]

The files are in the mail...

Thanks. Got it and will report back after I've had a chance to investigate.

[Albert Wiersch]

I tried this in v9.0 BETA 2 (are you using BETA 2?). I opened all the documents you sent and hit F6 to validate them and was not able to reproduce the error you mention. Can you provide more information?

[Baretull]

Yes, V9.00 BETA 2 (V8.9920). Verified as latest beta by internet check.

I've now uninstalled all previous versions, and installed BETA 2 again, and I find that the issue occurs if you increase the number of errors and warnings in the 'validator engine options' (the number varies, but 40 should create the error in all the documents).

Edit: I've sent off another batch of automated error reports as well.

Edit2: I think I've cracked it. It seems to be some sort of illegal return codes (line changes) in the java script at the end of the documents.

[Albert Wiersch]

Thanks! I've reproduced the problem and am tracking it down. I've eliminated the possibility of this exception but am trying to find out why the situation that caused it was happening in the first place.

UPDATE: I believe this is caused by a bug in JavaScript Lint that doesn't give CSE HTML Validator the correct line number (and thus causing the exception in v8.9920). I have reported this to the developers of JavaScript Lint.