Spin/Rotate Globe issue while accessing from US region
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
mapbox-gl-js version: v2.14.1
browser: Chrome
Steps to Trigger Behavior
- Login from US region
- Open a demo link - https://docs.mapbox.com/mapbox-gl-js/example/globe-spin/
- Globe rotation does not work and throws an error as below
camera.js:1252 Uncaught RangeError: Maximum call stack size exceeded
at Map.easeTo (camera.js:1252:19)
at spinGlobe (globe-spin-demo.html:1:1706)
at Map. (globe-spin-demo.html:1:2041)
at Map.fire (evented.js:130:26)
at Map._afterEase (camera.js:1438:14)
at camera.js:1374:18
at Map._ease (camera.js:1717:13)
at Map.easeTo (camera.js:1372:14)
at spinGlobe (globe-spin-demo.html:1:1706)
at Map. (globe-spin-demo.html:1:2041)
Link to Demonstration : https://docs.mapbox.com/mapbox-gl-js/example/globe-spin/
Expected Behavior
Actual Behavior
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 globe-spin demo and trace spinGlobe through Map.easeTo in camera.js, using the reported stack frames in evented.js as context. Reproduce the US-region failure in Chrome with v2.14.1, then confirm that globe rotation no longer causes the reported maximum call stack error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100