search

gcode-mirror / earth-api-samples

Automatically exported from code.google.com/p/earth-api-samples
0 stars 0 forks source link

Please support Google Chrome Browser #69

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Please support Google Chrome Browser.

Original issue reported on code.google.com by timhavens on 9 Sep 2008 at 6:45

GoogleCodeExporter commented 9 years ago 
There is still one blocking issue related to balloon contents that
we're still working on. Here is the public issue in Chrome that, once
fixed and released, should allow us to turn on Chrome support in the
Earth API:

http://code.google.com/p/chromium/issues/detail?id=1788

In the meantime, we have implemented a *temporary* hack that allows
you to bypass our browser detection process. To test your Earth API
page in Chrome (everything but balloons should be functioning), append
#geplugin_browserok to the end of your URL, i.e.:

http://code.google.com/apis/earth/#geplugin_browserok

WARNING: Do not use this hack for anything but testing purposes, as it
is subject to change or removal at any time.

Just to reiterate, even with this *temporary* hack, balloons will not
work until the Chrome issue mentioned above is resolved. Once it's
resolved and end users receive the update, we will enable Chrome
support in the Earth API.

Original comment by api.roman.public@gmail.com on 5 Nov 2008 at 6:37

GoogleCodeExporter commented 9 years ago 
Can we expect that geplugin will support specific version of webkit or just 
chrome
browser? I'm asking this because adobe air is also using webkit and I'm 
interested to
use it in air application via it's embeded browser. Any chance this could be 
possible
in the near future?
Thanks,
Milan

Original comment by kosir.milan on 25 Nov 2008 at 1:58

GoogleCodeExporter commented 9 years ago 
The release 154.10 (which should contain the fix for the issue : 
http://code.google.com/p/chromium/issues/detail?id=1788 ) is already out by now 
(Chrome v 1.0.154.39 isn't it) ?

Why is then still the temporary hack required and is the Google Earth Plug-in 
not yet 
avialable for all Chrome users and for all examples ?

Original comment by jjnhendr...@gmail.com on 19 Dec 2008 at 1:50

GoogleCodeExporter commented 9 years ago 
There are still a few issues that we need to work out before we can turn on 
Chrome
support. Sorry for the delay!

Original comment by api.roman.public@gmail.com on 19 Dec 2008 at 6:20

GoogleCodeExporter commented 9 years ago 
Any updates on this Roman. Last update was Dec19, 2008.
Chrome supported yet ?

Original comment by ged...@gmail.com on 11 Feb 2009 at 2:15

GoogleCodeExporter commented 9 years ago 
We've just launched support for Google Chrome 1.0+.

There are some more details at the new Google Earth API notifications group, 
which I
recommend that you all either join or subscribe to via RSS:

http://groups.google.com/group/google-earth-api-notify/topics

****NOTE 1****
There's a known bug where the plugin fails to load on Chrome 2.0 (developer 
channel)
running on Windows Vista.
********

****NOTE 2****
There is one open bug that is important to take note of, as it may
require a slight change to your site:

http://code.google.com/p/chromium/issues/detail?id=7793

The issue is that Chrome temporarily hangs when alert/prompt dialogs
are opened in an API callback or event handler routine. The workaround
is to wrap all calls to alert or prompt in a setTimeout, as is
demonstrated in the Fetch Bad KML sample:

http://earth-api-samples.googlecode.com/svn/trunk/examples/kml-fetch-bad.html
********

Original comment by api.roman.public@gmail.com on 20 Feb 2009 at 12:16