> That's your book. > In my book, it is discourteous towards the volunteers who answer > questions in the forum, to ignore the group's posting guidelines, and > refuse to post a link.
I wasn't looking for diagnostic help, just an answer to a single, relatively basic question. The community guidelines do not apply to simple questions like that. Please read what is written, instead of assuming I want to affront you and everybody else on the forum. I do not and would not and the only umbridge I take is with your assumption that I do. On Dec 15, 3:09 pm, Rossko <[email protected]> wrote: > 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. > Indeed. I apologise for that. > > 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. Agreed. Though I was asking a question and not asking people to diagnose anything... but I can see how people would assume I might. > 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. It's a similar train of thought to one we're on, but we've not any success thus far. We all use SVG-compliant browsers though and, in fact, we're working with Mozilla to bring one of their products up to standard in that regard to meet the requirements of this product. The issue has been tested across various browsers. One thing that has changed is our internet facilities and we're looking into that as a possible issue. The consistency of the issue is a factor in that respect, though, as we can duplicate consistent issues. If we come across anything and it turns out it is Google we'll surely . -- 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.
