Clicking on cluster at max zoom level causing GMap loading issues
It seems there is a communication problem between the marker clusterer app and the Google maps app when the map is at max zoom level. Either the map doesn't know what to do with itself when it receives a back-door request to zoom in (from cluster click) but it can't, or the clusterer doesn't know when to not send a zoom request.
This should be fixed before the KNB announcement in early January.
Updated by Lauren Walker almost 10 years ago
- Status changed from New to Resolved
The GoogleMaps was freezing up (and crashing the browser in some instances) when a cluster was clicked on at max zoom level. I found that the markerclusterer plugin has trouble syncing the Google Map max zoom property and the MarkerClusterer max zoom property. When I set the clusterer max zoom to 15 and the map max zoom to null, everything seems to work okay. Any other combination triggers a map event (either fitBounds or zoom), triggering many metacat searches and freezing up the map.
This issue also caused me to notice that at max zoom, if you click on a cluster, the cluster disappears. So I patched the MarkerClusterer plugin to fix that according to https://code.google.com/p/google-maps-utility-library-v3/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Status%20Priority%20Fixed%20Owner%20Summary%20Stars&groupby=&sort=&id=210.