On Jun 26, 5:34 am, HostGIS Support <[email protected]> wrote: > > I have the simplified example here which still shows the bug. As you can > see, there's not much to debug: a map is created and 2 KmlLayers are loaded. > http://klamathinstitute.org/gm3kmltest/ > With this example, I can click the markers in IE8, but it doesn't work in FF3.6
In IE8 I see the boundary on top of the markers (drawn after the markers) but in FF I see the boundary drawn first. The display order of KML layers is determined by the response order from the google servers following the setMap() calls. I think this is a bug. The order of setMap() calls should be respected by the API. A workaround to make the layers display in correct order was demonstrated on this thread: http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/d141c913badec13a Taking that technique further, we can display the 2 layers in the following orders: Basin first, then Points http://www.william-map.com/20100626/1/basin_points.htm Points first, then Basin http://www.william-map.com/20100626/1/points_basin.htm it seems the points are clickable if they are drawn first. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
