alternative maxBounds implementations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
Map.maxBounds (red box) is implemented as never show the area outside the maxBounds (blue box, must be strictly within red box) . While useful in some contexts it has limitations on zooming out, which is sometimes not desirable.
An alternative approach to maxBounds is to ensure that at least some part of these bounds is shown in the map, potentially with a padding (green box must have some part in the red box).
Another alternative is to stick with the current approach but add a padding in pixels to the maxBounds.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Map.maxBounds behavior described in the issue and compare the existing constraint with the two proposed alternatives: allowing part of the bounds to remain visible or adding pixel padding. Before implementation, clarify which behavior and API are desired; done means the selected maxBounds approach is specified and its zooming behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100