Some sites want to control the z-indices of their markers. If we were to add an API-computed z-index to their z-index, that could change the ordering of their markers. So if a site wants to control the z-indices of their markers, we should do exactly what they say.
The issue here is that some sites are happy with the default z-indexing (by height), but want to bring a marker to the front on hover. Whether we added their z-index to ours, or obey their z-index directly - they still need to use a sufficiently large value to ensure their marker appears in front of everything. So either the API must provide a "maximum z-index" promise, which would be the maximum z-index the API would assign to a marker, or the API must provide explicit support for hover. On Thu, Mar 3, 2011 at 11:26 AM, Esa <esa.ilm...@gmail.com> wrote: > Why not add user zIndex to your internal zIndex? > > -- > 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. > > -- 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.
