> This is typical, if You use products from different producers. It's > always the other product, which causes the problem! > I'm 100% sure, that in bing forum everyone would say: That's Google > maps, bing works perfect & doesn't cause this issue.
I agree, it is always difficult to get past the finger-pointing stage when there are mixed products involved. It would be better to do a bit less finger-pointing, and keep an open mind. I should have clarified my meaning "the problem may lie in the Bing area" by adding " .. or in the Google API or in webkit". It's good you've now reported your issue number, so that anyone else interested can add their 'star' to it. Disappointing that it goes unacknowledged. That slimmer example you were goint to cook up would help anyone investigating, the page hits 3Mb when maps are shown. Have you considered using some hide/show mechanism for map switching, rather than z-index? I can't even find your switching code. -- 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.
