So if that code is fine... is there a related bug that would explain the
problem? It handles the layers a little strangely too, in resizing and
rendering while the page loads, which I can compensate for easily enough
when I'm doing the layout... and I can deal with the flash not working
in layers, I really don't need to use the flash, it's just a nice touch
as far as being able to use more intersting fonts, etc. without
incorporating larger graphics formats (.gif, .jpg) - just wondering if
anyone knows if this is something being looked into already...
thanks :)
Patrick
Jason Johnston wrote:
> No, that code is fine. It's the function Macromedia uses to get the
> correct object reference depending on the browser's object model. It
> works in the document.layers, document.all, and W3C-DOM models.
>
> --J
>
>
>>
>> I'd be willing to bet that the problem is this code:
>>
>> function MM_findObj(n, d) { //v4.01
>> var p,i,x; if(!d) d=document;
>> if((p=n.indexOf("?"))>0&&parent.frames.length) {
>> d=parent.frames[n.substring(p+1)].document; n=n.substring(0,p);}
>> if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++)
>> x=d.forms[i][n];
>> for(i=0;!x&&d.layers&&i<d.layers.length;i++)
>> x=MM_findObj(n,d.layers[i].document);
>> if(!x && d.getElementById) x=d.getElementById(n); return x;
>> }
>>
>> The for loop uses "d.layers". Mozilla doesn't support
>> the layers member of document objects.
>>
>>
>>
>
