On Apr 29, 1:42 pm, "Dann (Google Employee)" <[email protected]> wrote: > Hey Brian, > > Thanks for bringing this up as a concern. Unfortunately, after > upgrading 2.s up to 2.193, prior versions will no longer be > accessible. In other words, there'll be no way to continue serving > 2.140. > > Do you have any specific data around how much slower polygons perform > in Opera? How about in later versions past 2.193? > > Thanks, > > Dann > Sorry it's taken me so long to reply, Dann. The problems that occur in Opera are not so much about the rendering speed, but rather Opera fails to render them properly. I have not tested every version, but 2.193 and the current version (v=2) both fail. I can try again with v=2.x, but not right away.
What Opera does, is render the polygons (usually) and then if you change zoom or move the map, the old polygons remain in the same location _relative to the div_, and new polygons show up in the appropriate place _relative to the map_. A few zooms/moves and there are polygons all over. With 2.140 everything works fine. See issue at: http://code.google.com/p/gmaps-api-issues/issues/detail?id=2219 Is there a reason Google can't make v=2.s --> 2.193 and still serve 2.140 at v=2.140? Just Google policies or is there a technical reason? Certainly seems like it can't be a storage space issue! -- 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.
