Chris: Setting optimized: false seems to have solved my problem since I was already doing everything else you suggested. Thanks.
Now I wish I could set optimized: true but for that I need an official way to access the internal z-indexes of the marker. (This is part of my work on MarkerWithLabel http://google-maps-utility-library-v3.googlecode.com/svn/tags/markerwithlabel/ , by the way.) Simon: you may want to try setting optimized: false to see if it helps your problem. With Safari/Mac, I also see that the marker with the higher explicitly-set zIndex appears in the background. Gary On Mar 17, 11:48 pm, Chris Broadfoot <c...@google.com> wrote: > Hi Gary, > > Because Markers are now rendered in Canvas tiles, a group of markers may > exist inside one DOM element. This makes it infeasible to order your own DOM > elements with in the overlayImage pane. So, the first step is to specify > optimized:false when instantiating your Markers. > > Doing so isn't a solution in itself. I take it you want to have a DOM > element match or closely relate to a particular Marker's z-index. The API > does not expose internal z-indexes, so the key here is to set z-indexes > yourself. This allows you to deterministically order your own DOM elements > amongst API Markers' DOM elements. > > When setting z-indexes yourself, you could employ a similar strategy to the > API. Setting z-index based on Mercator y-value and/or latitude is a good > starting point. > > Hope that helps, > Chris > > --http://twitter.com/broady -- 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 google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
