leecade / leecade/react-native-swiper
Conflict in swiping between tab navigator and the swiper component
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
OS : Android
Versions:
React native swiper: latest
React native: latest
Expected behaviour
If the user swipes the part of the screen that holds the swiper it should, the swipe should only affect the swiper.
If the user swipes other parts of the screen, it should affect the tab navigator and navigate to the next screen.
Actual behaviour
Sometimes when the user swipes the swiper part of the screen the navigator navigates to the next screen.
You can simply produce the problem but having a swiper component places in one of the tab navigator screens.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue on Android with a swiper component placed in one of the tab navigator screens. Start by examining how the swiper and tab navigator handle swipe gestures, then verify that swipes inside the swiper affect only it while swipes elsewhere navigate between tabs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100