I'm finding that it comes from the (packed) Validation plug-in script. I think it might need a semi-colon at the end of that whole packed string. Try adding that manually and see if it makes a differences. Try the min version also if you haven't.
On Feb 6, 6:30 am, Tintin81 <tkleem...@gmail.com> wrote: > Hi Henry, > > Thanks you very much for your help. I have eradicated the comma and > also did some other polishing work, but nothing has changed :-( > > The error message I am getting in Internet Explorer 6 is still the > same. What bugs me is that Internet Explorer doesn't tell me the exact > name of the file that the error comes from. > > It is constantly referring to a missing semicolon, but I can't figure > out where that might be. Not even in which file... > > Can anybody come to the rescue? > > Thanks for any help in this matter... > > On Feb 6, 12:40 pm, Henry <rcornf...@raindrop.co.uk> wrote: > > > On Feb 6, 10:30 am, Tintin81 wrote:> I am new to Javascript and implemented > > a few nice JQuery > > > features on <a href="http://new.designbits.de";>my new > > > website</a> . All of them work great in Firefox and Safari. > > > > In IE6, however, the site looks like a mess, even with > > > Javascript enabled in the options panel. > > > <snip> > > > There are two JScript errors reported as that page loads in IE. The > > first is a complaint about a missing ';' (and you will have to track > > down yourself), the second is in your functions.js file where you > > have:- > > > $.extend($.validator.messages, { > > required: "", > > email: "", > > > }); > > > - in which an object literal's contents end in a comma. This is a > > syntax error by ECMAScript rules, and so should be expected to be a > > syntax error in browsers that implement the ECMAScript standard (such > > as JScript in IE (more or less)). The ECMA standard allows syntax > > extension and JavaScript(tm) (and good JavaScript(tm) imitators) take > > advantage of that to be more tolerant of commas at the end of object > > literal contents than they need to be (as the extra commas do not > > result in ambiguities). JScript doesn't and so sees the comma as a > > syntax error, and so that is a very likely cause of differences in > > behaviour between IE and other browsers. Particularly if the behaviour > > on IE looks like total failure to act on a script. > >
