Im getting some strange problems.
I have a "click" event listener on ge.getWindow(). That checks
event.getTarget(); if its a KmlPlacemark, it iterates over a list of
placemarks comparing them to event.getTarget(). If it finds it, it
takes an action.
This works in IE6, IE7, FF2 and FF3. In chrome, it never finds the
placemark in my list. I've even cut the example down to where there is
exactly one placemark, and it still doesnt compare equal.
In other words event.getTarget() == myPlacemark *always* returns
false. But if I compare the locations of the placemarks, and the
descriptions, and the names they are obviously the same placemark.
My workaround for now is to give the placemarks an Id, and compare the
Id's for equality.
Is this a known bug?
Mark
On Feb 19, 4:12 pm, Roman N wrote:
> Hi all,
>
> 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****
> 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-...