Thanks Ben, After some more tests, the behaviour in Firefox should be defined as "undefined". I have tried assigning by own, arbitrarily defined, zindex scheme ... and all works as desired.
Thanks for all of the constructive help given. On Feb 1, 1:13 pm, Ben Appleton <apple...@google.com> wrote: > Right; if you want to robustly control the placement of your markers you > should specify a zIndex for each. > > On Tue, Feb 1, 2011 at 1:04 PM, sgiddings <mr.s.giddi...@gmail.com> wrote: > > I mention this because, in Firefox, I can access the z-index correctly > > through getZIndex and thus place my flag "behind" the poi marker. > > > Following your remarks, does this mean that I can create my own "z- > > index" values, ie starting from 0, without the risk of having markers > > badly positioned in the hierarchy ? > > > On Feb 1, 11:54 am, Ben Appleton <apple...@google.com> wrote: > > > It is intended that you cannot access the final zIndex that has been > > > assigned to the marker. The final zIndex assigned by the API is subject > > to > > > change as it depends on the underlying implementation. You can access the > > > zIndex that you set, which is undefined in this case. > > > > This behavior is consistent between browsers. Why do you mention IE in > > the > > > title of your post? > > > > You will find this group much more helpful if you post a link to a site > > that > > > replicates the issue. > > > > On Tue, Feb 1, 2011 at 11:06 AM, sgiddings <mr.s.giddi...@gmail.com> > > wrote: > > > > After having made deeper investigation, I discover that, when markers > > > > are inserted into the display, they are given a z-index within the > > > > style attribute of the container div. > > > > Here is an example of what is generated within IEv8 by simply creating > > > > a marker and NOT calling setZIndex : > > > > > <div style="z-index: 24; position: absolute; filter: alpha(opacity=1); > > > > width: 32px; height: 37px; overflow: hidden; top: -13px; cursor: > > > > pointer; left: 373px" class=gmnoprint title="">...</div> > > > > > When I call the method getZIndex, should it not therefore return the > > > > value indicated in the z-index css style ? > > > > Is there a correct means to be able to access the div DOM element to > > > > query for this value within the attributes property ? > > > > > On Feb 1, 10:15 am, sgiddings <mr.s.giddi...@gmail.com> wrote: > > > > > For Paulo - > > > > > It is obvious that you have not taken the time to correctly > > understand > > > > > my post. > > > > > I indicate two aspects - the site is still in DEV, therefore not > > > > > visible, so no demo ! > > > > > Secondly, the information given was sufficiently detailed and clear > > > > > permitting Rossko to give a very pertinent reply. > > > > > Try better next time. > > > ----------------------------------------------------------------------- > > > > > For Rossko, > > > > > > Thankyou for your helpful reply. > > > > > Indeed I had noticed a number of questions going around about this > > > > > subject, but had not picked up on this aspect. > > > > > You are right, I do not set the zIndex of the poi markers beforehand. > > > > > Indeed I cannot see how this could be possible as, in IE, I would not > > > > > be able to determine the correct starting index. > > > > > Yet again more cross browser dev headaches. > > > > > > On Jan 31, 9:48 pm, Rossko <ros...@culzean.clara.co.uk> wrote: > > > > > > > > However, in IE v8, the call to Marker.getZIndex always returns > > > > > > > undefined. > > > > > > > Has anyone else come across this problem? > > > > > > > It's been mentioned in this group before that it only returns a > > > > > > meaningful value if you have previously defined it using setZIndex. > > > > > > Without the context of seeing your code in action, can't say if > > that > > > > > > is relevant. > > > > > -- > > > > 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<google-maps-js-api-v3%2bunsubscr...@googlegroups.com> > > <google-maps-js-api-v3%2bunsubscr...@googlegroups.com<google-maps-js-api-v3%252bunsubscr...@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<google-maps-js-api-v3%2bunsubscr...@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.
