Thats not really a good idea, because none has no real value. So you
are assigning undefined as a background image. Sure it may work, but I would argue
that the real image solution is cleaner.
Rob
On 11/1/2001, Richard Bennett wrote:
> Could people running https:// please confirm this works?
> It's a lot cleaner than using an image, but I would like to be sure it works for
>everyone, before changing a working setup.
> To test, change line 156 in src/lib/dynapi/api/dynlayer.js from:
> if (is.ie55 && this.bgImage==null && this.html==null) s+='
>background-image:url('+DynAPI.librarypath+'dynapi/images/common/transparent.gif);';
> to:
> if (is.ie55 && this.bgImage==null && this.html==null) s+='
>background-image:url(none);'
> and see if your pages still run over a secure connection.
> (and if transparent layers still catch events in IE5.5)
> Thanks for the fix Doug.
> Richard.
> ----- Original Message -----
> From: Doug Melvin
> To: [EMAIL PROTECTED]
> Sent: Wednesday, October 31, 2001 9:14 PM
> Subject: [Dynapi-Dev] note:
>>[*] Old IE5.5 event fix, which used a javascript:null as background image for empty
>layers, had to be
>>changed into using a real transparent gif which is supplied with the standard
>distribution, due
>>to that javascript:null image causing a warning when using DynAPI via a secure
>server (https://)
> this is not entirly true.
> I fixed this in our app by making:
> if (is.ie55 && this.bgImage==null && this.html==null) s+='
>background-image:url(javascript:null);'
> into:
> if (is.ie55 && this.bgImage==null && this.html==null) s+='
>background-image:url(none);'
> The error went away (HTTPS:// secure error that is)
> Somehow I think this is a little easier than loading an actual image.
> If someone can prove that this fix does not work you better damn well tell be before
>we deploy this $45m application..
> please?
> :-)
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://www.mail-archive.com/[email protected]/
