Title: Resizing in Netscape - Source of the problem
That's nice. I've never seen the compatibility matrix before. It says that the dynimage doesn't cause any JS errors. In my experience, the DynImage is responsible for the this.elm has no properties error.
-----Original Message-----
From: Raymond Smith [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 20, 2001 12:24 PM
To: [EMAIL PROTECTED]
Subject: Re: [Dynapi-Help] Resizing in Netscape - Source of the problem

If you look at the compatability matrix you can see that DynImage is the last nasty impacting NS on the Win Platform.
 
----- Original Message -----
Sent: Tuesday, February 20, 2001 11:04 AM
Subject: [Dynapi-Help] Resizing in Netscape - Source of the problem

I have read the mailing list history and see that many people have had problems with resizing in Netscape. I got the error 'this.elm has no properties' too

Through testing, I discovered that netscape has no problem with the resizing until you use a DynImage.

Maybe this is old news but Netscape calls the DynAPI.onResize function no problem until you add a DynImage. (At least on my machine. (WinNT 4, Netscape 4.7)

When I removed all my DynImages and replaced them with layers with an image on them (myLayer.setHTML("<img src=myimage.gif>");) everything worked fine.

The this.elm error occurs on line 415 of dynlayer.js but that is only when setHTML is called from the dynimage.js file. This is probably because the dynimage file does not have an elm variable. So I thought that maybe there was someone out there that had been using DynAPI for more that 2 days who could fix the problem. I was unsuccessful.

But then, maybe this isn't the source of the problem at all. :-)

Jordan


Reply via email to