Hectic behavior of gestures when using cooperative gesture handling on Android
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
Cooperative gesture on Android result in various inconsistency and hectic behaviors, where the gesture being recognized is a bit random, making the map hard to navigate.
**mapbox-gl-js version**: main
Tested on Android galaxy s5 edge. When used along
### Steps to Trigger Behavior
1. Open the example https://github.com/mapbox/mapbox-gl-js/blob/main/debug/scroll_zoom_blocker.html on an Android phone.
2. Try to trigger a 2 finger gesture
https://user-images.githubusercontent.com/7061573/164798512-e06a7fc4-db7e-472d-9d88-13025dd2231f.MOV
### Expected behavior
1. Cooperative gesture handling behave the same as on iOS
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 debug/scroll_zoom_blocker.html example and reproduce the two-finger gesture on an Android phone, then compare its behavior with iOS. Trace the cooperative gesture handling entry point used by that example; done means Android recognizes gestures consistently and behaves like iOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript, typescript
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100