Allow options to be passed to Map.setMaxBounds #1834
Merged
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
…used when setting the view.
davidjb
added a commit
to davidjb/Leaflet
that referenced
this pull request
Jul 5, 2013
mourner
added a commit
that referenced
this pull request
Jul 11, 2013
|
Thanks, merged. |
mourner
added a commit
that referenced
this pull request
Jul 17, 2013
Document changes to setMaxBounds method as per #1834
mourner
added a commit
that referenced
this pull request
Jul 17, 2013
…-pages # By David Beitey # Via David Beitey (1) and Vladimir Agafonkin (1) * 'gh-pages' of https://github.com/Leaflet/Leaflet: Document changes to setMaxBounds method as per #1834
davidjb
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.
Allow options to be passed to Map.setMaxBounds such that they can passed through to setView. Without this, animation (zooming/panning) can't be customised. In my specific use case, I do this:
to just force the map to go to those bounds without panning or zooming.
This is my first pull request -- so when I'm updating documentation regarding this, I'll need to have another pull request for that. Should I do that now or wait for this to accepted?