> How do I figure out why it is not working for me or any of my coworkers?
Doesn't work for me sometimes, in FF2. In fact it seemed to work first off but not on reloads - is that a clue about client side caching? Works when zoomed in tighter. "not working" is apparent as the mouse pointer failing to change when moved over 'clickable' areas. > What factors could effect how the map and the click event loads? The source KML is fetched from Google's servers and cached at Google ; any issue with that should be consistent? Or would it ... the processing of multiple files might include random who-goes-first effects. There it gets rendered into tile images the client fetches, and some JSONy stuff that the client uses for managing clicks. The images are fetched at each zoom level, but I suspect the clicky stuff is one- time. How does Google manage this when multiple KML requests are fired at it in series? Is that what's going wrong? We might imagine the Google server starting to build the JSON for the fourth time when once again another add-on KML request arrives ... In Firebugs NET tab I can see an error 500 from http://mt1.googleapis.com/mapslt/ft?hl=en-US&lyrs=kml%3AcFw2ptw ... &callback=_xdc_._l3edun&token=102928 and I'd guess that is the clicky stuff going wrong Have a look at this thread for a technique to load multiple KML in a serial controlled fashion http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/7cfdbd634a7cb456/aa3a8dee6bfaf02c worth testing perhaps -- 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.
