DNS ERROR behind balloon

[Bob Lytle]

When viewing a placemark description in a balloon, an IE dns error
appears layered behind the description. The text is the familiar,
generic error page built into IE: "Internet Explorer cannot display
the webpage, most likely causes: You cannot connect to the
Internet, ...". This occurs on a Vista box with IE7 but does not
occur on an XP box with IE6. It does not occur with Firefox, which
displays fine on both systems.

An earlier post (April) suggested that this only occurs when the html/
jsp page is located on the local machine and opened directly. I have
also deployed the file to a remote web/app server and the issue still
occurs.

Thanks for any information on this.

Bob.

[Bob Lytle]

I believe I finally isolated this. This occurs when I have the width
of the plugin div tag set to 739px or greater and only when viewing in
IE7. A width up to 738px is normal but 739px displays the error
behind the balloons.

Bob.

[DougH]

I'm using Internet Explorer 8 with Windows XP, and I still have the
problem after setting the width to 700px. Are you sure you no longer
have the problem when you make those changes, or you just can't see
it? I can clearly see the problem using Internet Explorer 8 with
Vista, but its more subtle with Windows XP. I originally discovered
the problem because I was having formatting problems, and a strange
tooltip show up in my balloons, rather than being able to actually see
the error page in the balloon, as happens with Vista.

There are at least two ways that I can detect the error page in my
balloons, even when I can't see them:

1) Move the mouse around the balloon until a unexplained tooltip
appears, or the mouse cursor changes unexpectedly, and View Source.
The source at those locations will be the error page, whereas the
source for every other part of the balloon will be your code.

2) Use Developer Tools in Internet Explorer 8 to look at the HTML. Go
through all the DIV tags that have been added to your plugin DIV until
you find one that contains <iframe submitName="iframeshim"... The
contents of that IFRAME will be the HTML of the error page.

The problem can also be detected indirectly by using IETab in Firefox,
and looking at the error console.

I compared the same page loaded locally and loaded from a server,
using both Windows XP and Vista, and only the local page exhibits the
problem. Apparently, different configurations, balloon contents, and
styles affect the problem so it might be impossible to find a work
around that always works. I've thought about programmatically
searching the DOM for the offending IFRAME and removing it, but I'm
not having the problem online, so it hasn't been a big priority.