failed to initialize when loaded from iframe

107 views
Skip to first unread message

cody hawke

unread,
Jan 2, 2009, 3:48:04 PM1/2/09
to KML Developer Support - Google Earth Browser Plugin
Hi all,
I have a page, 'GEinstance.html", that contains a google earth plugin.
Whenever I open this page in a browser, it works fine.

However, I need it to be accessed via an iframe. When creating an
iframe with src="GEinstance.html", the iframe shows up properly but I
receive this error:

"The Google Earth Plugin failed to initialize. Try reloading the page.
If that doesn't help, you can re-install the Google Earth Plugin using
this link".

I've tried reinstalling several times but to no avail. The HTML page
that contains the iframe is on a local machine and needs to be there.
Does anyone have ANY idea what could be wrong?
Thanks,
Cody

cody hawke

unread,
Jan 2, 2009, 4:10:05 PM1/2/09
to KML Developer Support - Google Earth Browser Plugin
Resolved.....It was causing problems because I was initially setting
the display:none property on the div containing the iframe......Since
then, I've set it to have a top:100000 value until it needs to be on
the page, at which time I just set top:100px and it's good to go. I'm
sure there's a more elegant way though. While I'm here.....Anyone have
any ideas?
Cody

fraser [Earth API Guru]

unread,
Jan 3, 2009, 7:22:58 AM1/3/09
to KML Developer Support - Google Earth Browser Plugin
Hi Cody,

Basically "display:none" removes an element completely from the
document - hence the errors when the plugin attempts to reference that
element.
As you just want to hide the element (not remove it) you could use
"visibility:hidden" instead.

I haven't tested this but I'm pretty sure it will work for you.

Anyway, I hope that helps,

F.
> > Cody- Hide quoted text -
>
> - Show quoted text -

Roman N

unread,
Jan 5, 2009, 1:11:30 PM1/5/09
to KML Developer Support - Google Earth Browser Plugin
Well, display:none doesn't exactly remove the element from the DOM,
but in many browsers, hiding an element using display:none has the
side effect of destroying any OS-level plugin windows 'contained'
inside that element. We have a fix in place that takes care of this in
basic cases; however, we're looking into better solutions for handling
plugin show/hide situations.

- Roman
Reply all
Reply to author
Forward
0 new messages