fix: Update calc clusters to happen after Idle event - reduces issue 563 #806
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR updates the
custom-marker-clustering
example to delay cluster rendering until the map becomes idle, rather than reacting to everybounds_changed
event during zoom.Motivation
While investigating issue #563, I found that the aggressive re-clustering during zoom gestures may contribute to a rare but severe bug where the zoom level resets unexpectedly (sometimes to zero). This is especially noticeable with a large number of markers. See comment.
By aligning the behavior with how Google’s official
[js-markerclusterer](https://github.com/googlemaps/js-markerclusterer)
(https://github.com/googlemaps/js-markerclusterer) handles clustering (listening to theidle
event), we reduce the likelihood of triggering this issue and improve performance during zoom gestures.