fix(bounds): support optional maxBounds for stricter position constraints#541
Open
sheikhshaheerimran wants to merge 1 commit intoBetterTyped:masterfrom
Open
Conversation
sheikhshaheerimran
force-pushed
the
fix/bounds-min-max-limits
branch
from
4e4c366 to
4b4efa1
Compare
…ints Allows users to define max bounds for pan/zoom behavior. This improves control over movement limits when the default limitToBounds is not sufficient. Previously, min and max positions for X and Y were not used to constrain the image bounds.
sheikhshaheerimran
force-pushed
the
fix/bounds-min-max-limits
branch
from
4b4efa1 to
56f4124
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR fix support for optional maxBounds in the pan/zoom calculation logic, allowing users to define stricter movement constraints beyond the existing limitToBounds behavior.
Why This Change
Previously, limitToBounds only used internally calculated bounds and ignored explicitly defined minPositionX, minPositionY, maxPositionX, and maxPositionY. This limited the developer's control over how far the content could pan or zoom.