Clear marker occlusion timer on Marker#remove #10478
Merged
+12
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andycalder
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes #10402 by clearing the marker occlusion timer on
Marker#removeand on the map'remove'event.I reproduced the bug by removing the markers from the
markers.htmldebug page while moving the map. I then verified that this change fixes the problem.Marker#removeis not currently covered by unit tests, and I don't see an easy way to test this functionality. Thoughts?Launch Checklist
mapbox-gl-jschangelog:<changelog>Fixed a bug where markers may throw an error after being removed from a 3D map.</changelog>