Excellent! Glad to see you figured that one out. Rest assured that
*every* web developer has pulled out hair related to that particular
issue. Fortunately, in many editors today, you can run a tool called
'jslint' that does a simple syntax check for you. In my editor
(TextMate), I actually have it set up to do that check every time I
save.
_jason
On May 26, 2:05 pm, colin_e <colin.ev...@nhs.net> wrote:
> Just to finish this one off, I discovered my problem in IE6 was
> nothing to do with the jquery search operation we were discussing.
>
> As I was working on the code I had added an object initialisation
> above the line in question that had an extra comma at the end, as in-
>
> var frames= {
> EM: 1*offset,
> .
> .
> .
> YH: 10*offset, //<<extra comma here
> };
>
> IE6 choked on this, whereas Firefox was quite happy with it.
>
> I've done enough little bits of Perl, PHP, and now JavaScript over the
> years that I have terrible trouble remembering exactly which bits of
> syntax will or won't work with each!
>
> Thanks again to Jason, my little dynamic map works like a charm.
>
> Regards: colin_e
>
> On May 25, 8:29 pm, kiusau <kiu...@mac.com> wrote:
>
> > On May 25, 3:44 am, Jason Persampieri <papp...@gmail.com> wrote:
>
> > > Certainly... you're really not all that far off at all... let me just
> > > point out a couple of things.
>
> > Very nice presentation!
>
> > It is likely that many novice users of jQuery will be able to benefit
> > from it. Please do respond to the originator's question about the use
> > of :first-child in IE, and suggest a work around if, indeed, it is an
> > issue.
>
> > Roddy
