Here is a publicly accessible version of the map in question. I've noticed sporadic lock ups of the initial Google base map, which pauses or aborts the loading of our subsequent overlay ImageMapType tiles and even some of our javascript UI components.
This "lock up" is not something I've seen in the past. It was something that I've noticed recently, possibly since the latest API release on Oct 11, but I didn't see anything in particular in the API changelog that could cause this issue. If anyone has any ideas or areas we can further investigate, I would greatly appreciate it! http://rootwireless.cnet.com/cnet/ Thanks, Lawrence. On Oct 19, 5:26 am, Chad Killingsworth <[email protected]> wrote: > Nope. Need a link to your map to see what's going on. > > Chad Killingsworth > > On Oct 18, 11:56 pm, Lawrence <[email protected]> wrote: > > > Recently I have noticed an issue where some of the base map tiles do > > not load or custom overlay map tiles do not load. This seems to cause > > some of my ImageMapType tiles to not get downloaded or some of my > > CustomMapType tiles to not get loaded. I assume my overlay map tiles > > require the base map tiles to load first in order to coord parameters. > > > Has anybody else noticed any recent strange behavior with map tiles > > not loading or causing your own javascript functions to abort? > > > Thanks! -- 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.
