This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
[core] Guard against camera's minScale
being NaN
#5693
Merged
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.
Fixes a bug where calculating a camera's padded bounds for a single point would cause division by zero, resulting in NaN for
minScale
. This invalidminScale
would then be used to create an invalid paddedcenterPixel
.This was introduced by 8e30a4a in #4285, where the scale and padding calculations were split.
The “Add Custom Callout Point” option in ios-app exercises this bug, where the map zooms in on a single annotation, à la:
/cc @brunoabinader @1ec5