1.32, 1.7 and 1.8 all show Internet Explorer 8 Error

[lorlarz@…]

jQuery 1.32, 1.7 and 1.8 all show Internet Explorer 8 Error on the first line of the jquery.js file: ILLEGAL CHARACTER. AND: This seems to prevent some programs from running: The following program runs with jQuery 1.26 ONLY IN INTERNET EXPLORER. I runs with all versions of jQuery in Firefox:

SEE:  http://mynichecomputing.org/RotBan/rotBanxx.html This runs only with 1.26, though everything has been done to make sure NO INCOMPATIBILITIES between 1.26 and older version OCCUR IN THE ON-PAGE CODE!!

[timmywil]

Your page does have invalid css.

Please ask for help on the  forums or the #jquery irc channel.

[anonymous]

Replying to timmywil:

Your page does have invalid css.

Please ask for help on the  forums or the #jquery irc channel.

I disagree. There are no css errors. Let me better edit my complaint and bug report:

jQuery 1.32, 1.7 and 1.8 all show Internet Explorer 8 Error on the first line of the jquery.js file: ILLEGAL CHARACTER. AND: This seems to prevent some programs from running: The following program runs with jQuery 1.26 ONLY IN INTERNET EXPLORER. It runs with all versions of jQuery in Firefox:

SEE:  http://mynichecomputing.org/RotBan/rotBanxx.html This runs only with 1.26, though everything has been done to make sure NO INCOMPATIBILITIES between 1.26 and NEWER version OCCUR IN THE ON-PAGE CODE!!

[dmethvin]

Honestly,

Please ask for help on the forums or the #jquery irc channel.

We're not equipped to do one-on-one support here in the bug tracker.

[timmywil]

Firefox ignores your css error. I only looked at your page for 2 seconds, but I would suspect that IE8 could take more issue with your css error.

 http://cl.ly/image/0A3k2u3Y0z2B

[anonymous]

I found the CSS errors, you were correct.

[lorlarz@…]

I never checked the css; it came from a book example I elaborated on. It is interesting that CSS errors come up in IE8 as JS errors and I never thought to look at the CSS, since the program did run with jQuery 1.26 IN IE8 with no problem (and, again, the errors indicated were JS errors).