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= {
In fact I tried an alert() to see what the code was doing, and it now
looks as if it's not running at all. Don't you just love IE6?
On May 25, 4:49 pm, colin_e wrote:
> I hate to say this but i'm using IE6 for compatibility testing because
> that (like it or not) is sti
all direct children of this that are 's, then filter out all
> remaning, but leave first children */
> $(this).children('a').filter(":first-child")
> /* get all direct children of this, grab just the first one, then
> filter out all remaining, but leave 's */
&
in Firefox :-} At the moment I don't have
an IE quivalent to Firebug so i'm slightly stuck on how to try to
debug it.
Anyway, in Firefox it works like a charm. Thanks for the help, much
appreciated!
Regards: colin_e
On May 25, 11:44 am, Jason Persampieri wrote:
> Certainly... you
ct (an ), return the class attribute of the first
anchor that is a child of the current item".
I suspect I haven't got the right idea at all, can anyone point me in
the right direction?
Regards: colin_e
5 matches
Mail list logo
