Banner Ad / IFrame blues

[crazyinsomniac]

Your banner add's, that are at the top of every page,
use < layer src='' > and < iframe src='' >.

Why?
Why not an < img src='' > tag?

The reason i'm asking is that sometimes, for whatever reason, my MSIE5.5 doesn't download the src='' of the iframe, and forwards me to a stupid Cannot Find Server error page.

When i hit the back button it displays the cached contents, and usually forwards me to the error page again.

Using an < img src='' > tag would fix this, because if the destination address was unreachable, all that would happen is a brokken image would be displayed in place of the banner ad.

 ______________________________________________
|_____¸.·ooO--(> cRaZy is co01. <)--Ooo·.¸_____|
 ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ

[kilinrax]

It's generally used to allow rich media ads (e.g. flash anims) to be embedded as well as images. Though this wouldn't solve the problem, a slightly better solution would be:

<NOLAYER>
 <IFRAME SRC="..." HEIGHT=60 WIDTH=468 MARGINWIDTH=0 HSPACE=0 VSPACE=0
+ FRAMEBORDER=0 SCROLLING="no" BORDERCOLOR="#000000">
  <A HREF="...">
   <IMG SRC="..." WIDTH="468" HEIGHT="60" ALT="Click Here." BORDER="1"
+ NATURALSIZEFLAG="0" ALIGN="TOP">
  </A>
 </IFRAME>
</NOLAYER>
<ILAYER ID="advert" VISIBILITY=hidden WIDTH=468 HEIGHT=60>
</ILAYER>

then at the bottom of the page:

<LAYER align=center SRC="..." visibility=hidden id=layer1 width=468 he
+ight=60 onload="moveToAbsolute(advert.pageX,advert.pageY); layer1.cli
+p.height=60;layer1.clip.width=468;visibility='show';">
</LAYER>

this causes netscape to load the ad after the page content, and then moves it to the position required.

[reptile]

I feel your pain. Usually if it's taking too long for the ad banner to load, I just hit the stop button and instead of the error taking up the entire page it puts the error page where the ad banner should be. It works fine that way (just a little annoying having to hit stop sometimes).

local $_ = "0A72656B636148206C72655020726568746F6E41207473754A";
while(s/..$//) { print chr(hex($&)) }

[buzzcutbuddha]

I'm using 5.5 and I have never experienced that problem....weird. Yeah, if the page is taking too long, just stop the browser and you should be fine.