[Dynapi-Dev] Note on ASP environment

2003-09-29 Thread Doug Melvin
For those who have no asp envirnoment, but would like one: www.domaindlx.com   100% Free asp hosting. 100 megs of space NO BANNERS!!! NO POPUPS!!! Database functionality included.   Not too slow either: http://a.domaindlx.com/DouglasMelvin/   ---Outgoing mail is certified Virus Free.Checked by

Re: Re[2]: [Dynapi-Dev] note:

2001-11-01 Thread Doug Melvin
<[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, November 01, 2001 2:31 PM Subject: Re: Re[2]: [Dynapi-Dev] note: > > - Original Message - > From: "Dougal Campbell" <[EMAIL PROTECTED]> > > > On Thu, 1 Nov 2001, Richard Bennett wrot

Re: Re[2]: [Dynapi-Dev] note:

2001-11-01 Thread Richard Bennett
- Original Message - From: "Dougal Campbell" <[EMAIL PROTECTED]> > On Thu, 1 Nov 2001, Richard Bennett wrote: > > > [...] > > I think you're right there, however I tried to check this, but couldn't > > replicate the bug this was supposed to fix. > > Wasn't it that in IE5.5 an empty layer

Re: Re[2]: [Dynapi-Dev] note:

2001-11-01 Thread Dougal Campbell
On Thu, 1 Nov 2001, Dougal Campbell wrote: > It has to do with SSL pages. If the DynLayer is from a page secured with > SSL, the "url(javascript:void)" syntax caused IE5.5 to complain about > unsecure elements in the page. I don't think mouse events were an issue > (unless there was some older re

Re: Re[2]: [Dynapi-Dev] note:

2001-11-01 Thread Dougal Campbell
On Thu, 1 Nov 2001, Richard Bennett wrote: > [...] > I think you're right there, however I tried to check this, but couldn't > replicate the bug this was supposed to fix. > Wasn't it that in IE5.5 an empty layer wouldn't catch mouse-events? It has to do with SSL pages. If the DynLayer is from a

Re: Re[2]: [Dynapi-Dev] note:

2001-11-01 Thread Richard Bennett
- Original Message - From: "Robert Rainwater" <[EMAIL PROTECTED]> > > {background-image: none} > > > ...without the "url()" enclosing it. > > Yes, in that instance none is correct (which is how is would be done > in css). But using url it is evaluated as an expression. The problem, > I t

Re[2]: [Dynapi-Dev] note:

2001-11-01 Thread Robert Rainwater
On 11/1/2001, Scott Andrew LePera wrote: > "none" actually is a proper value, but it should be expressed this way: > {background-image: none} > ...without the "url()" enclosing it. Yes, in that instance none is correct (which is how is would be done in css). But using url it is evaluated as a

Re: [Dynapi-Dev] note:

2001-11-01 Thread Doug Melvin
> > > 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. > > "none" actually is a proper value, but it should be expressed this way: > >

Re: [Dynapi-Dev] note:

2001-11-01 Thread Scott Andrew LePera
Robert Rainwater wrote: > 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. "none" actually is a proper value, but it should be expressed this

Re[2]: [Dynapi-Dev] note:

2001-11-01 Thread Robert Rainwater
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: >>[*]

Re: [Dynapi-Dev] note:

2001-11-01 Thread Richard Bennett
n 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, w

[Dynapi-Dev] note:

2001-10-31 Thread Doug Melvin
>[*] 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: