Let's go back a step ... > I wasn't stating there was a bug in the Google API.
Readers may have been misled by your chosen post titling "v2 Stable Bug" so you may have to forgive them jumping to that conclusion. > The code and data was stored inside a virtual machine, so the > environment is identical with the exception of the network surrounding > it. People will also make experience-based assumptions about your problem, in the absence of being able to check. Making those kind of assumptions is good diagnostic practice for working towards a quick solution. The most common root cause of postings here with "My map suddenly stopped working, I haven't done anything" is because the dataset has changed. The most common root cause of "My map suddenly looks funny, I haven't done anything" is because someone else has changed some CSS or added some unrelated code that tramples on an in-use variable name. The common subtext is of course that something HAS changed but hasn't been thought of yet, ruling out API change is of course smart and that's done now. That doesn't help with your problem, since you've ruled it all out apparently; but does explain why people are trying to offer the suggestions to be help you. I'll offer another guess based on your pointer to the network. Bear in mind that in some browsers, polys are rendered at Google's servers and requested by the API as image overlays. More rarely (and harder to spot) is that there has always been a timing race in the code, and some external change in latency is now exposing it. -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en.
