Old iphones required that DOM elements have a z index before they would respect CSS overflow:hidden. I'll take a look to see if more recent builds have fixed that bug.
Meanwhile, you should be able to work around this issue by putting your map div inside a containing div with a z index. Cheers Ben On Thu, Jan 13, 2011 at 4:34 AM, AirTime <[email protected]> wrote: > I have a page with multiple div containers with content. Then there is > another container holding an absolutely positioned V3 map window div. > No matter what values I choose for z-index for all concerned > containers, the map window always moves to the background once it's > fully loaded. I can see the border of the div in the foreground until > the actual map is showing then it's suddenly in the background. > > The problem seems to be that all the divs loaded by the maps api, > which show up with Chrome's code viewer, have a style-tag with tons of > stuff in them including an z-index:0 which obviously renders my z- > index:1000 from my css file void. > Is there any option in V3 to set a global z-index that the subdivs > adhere to? > > Needless to say everything worked fine with a V2 iframe... > > -- > 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]<google-maps-js-api-v3%[email protected]> > . > 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 [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.
