Jest: with the hook API, raw touch events fired under a `GestureDetector` don't reach ancestors under Testing Library 14
I maintainer di solito rispondono entro 2 giorni
@aliassar ci sta già lavorando.
Dal 2/11/2026.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 66/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- react-native, typescript
Direzione di ricerca
Start with the Jest mock at src/mocks/hostDetector.tsx and the hook detector at src/v3/detectors/NativeDetector.tsx, then reproduce the failing case from the linked repository with npx jest. Check how the mock and detector interact with Testing Library 14's touch event handling. Done when the parent receives touchStart in Jest under a hook gesture and the builder API case still passes.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Description
This happens only in Jest: it's an interaction between Gesture Handler 3's test stand-in and React Native Testing Library, not a bug in the runtime.
Under Jest, jestSetup.js replaces HostGestureDetector with a plain View (src/mocks/hostDetector.tsx at v3.3.0). For a hook gesture, NativeDetector passes that View its onStartShouldSetResponder (NativeDetector.tsx#L76 at v3.3.0), which declines the responder.
Testing Library 14 treats a declining responder as blocking every event for the ancestors above it, raw touch events included. So fireEvent(child, 'touchStart') under a hook gesture's GestureDetector no longer reaches a parent's onTouchStart. On a device it does. (Once a gesture activates on a device, the ancestors get touchCancel, as expected: that isn't what this is about. In Jest, touchStart and the moves before activation never reach them.) With a builder-API gesture, no such View is rendered and the touch gets through, so tests that passed on 2.x start failing after moving to the hooks.
The root cause appears to be on Testing Library's side: on a device, raw touch events reach every ancestor whatever the responder does, and Testing Library applies the responder rule to them anyway. I've reported it there as callstack/react-native-testing-library#1957. I'm raising it here too because Gesture Handler 3 users will run into it when they move tests from the builder API to the hooks, so you may want to do something about it on your side, or at least be aware of it.
Steps to reproduce
- Clone https://github.com/jrmsayag/rntl-touch-bubbling-repro-demo and run
npm ci. - Run
npx jest. - "with a hook-API gesture (usePanGesture())" fails: the parent's
onTouchStartgets 0 calls. "with a builder-API gesture (Gesture.Pan())" passes.
function Pannable() {
const gesture = usePanGesture({});
return (
<GestureDetector gesture={gesture}>
<View testID="child" />
</GestureDetector>
);
}
it('a raw touchStart under a hook gesture reaches the parent', async () => {
const onTouchStart = jest.fn();
await render(
<GestureHandlerRootView>
<View onTouchStart={onTouchStart}>
<Pannable />
</View>
</GestureHandlerRootView>,
);
await fireEvent(screen.getByTestId('child'), 'touchStart');
expect(onTouchStart).toHaveBeenCalledTimes(1); // fails: 0 calls
});
A link to a Gist, an Expo Snack or a link to a repository
https://github.com/jrmsayag/rntl-touch-bubbling-repro-demo
Gesture Handler version
3.3.0
React Native version
0.88.1
Platforms
Android, iOS (it happens in Jest, whatever the platform)
JavaScript runtime
Hermes (not relevant: Jest runs on Node)
Workflow
Using Expo Prebuild or an Expo development build (the repro itself is plain React Native with @react-native/jest-preset)
Build type
Debug mode
Device
Not applicable (Jest); pick any.
Device model
Not applicable (Jest, Node 22). @testing-library/react-native 14.1.0, Jest 30.5.2.
Acknowledgements
Yes
- Lingua principale
- TypeScript
- Stelle
- 6.8k
- Fork
- 1.1k
- Merge medio
- 1g 23h
- PR unite (30g)
- 46
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di software-mansion/react-native-gesture-handler
-
[Jest][3.5.0] `fireEvent.press` no longer reaches `Touchable` when its child is inside an `InterceptingGestureDetector`Forse già presa @m-bert l’ha presa 3 giorni fa. ApertaMissing info Platform: Web
Difficoltà 3/5 1-2 giorni Idoneità per principianti 72/100
software-mansion/react-native-gesture-handler#4689 · 4 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
[Web] GestureDetector blocks context menu by defaultForse già presa @lassiecoder l’ha presa 4 giorni fa. ApertaPlatform: Web
Difficoltà 3/5 1-2 giorni Idoneità per principianti 56/100
software-mansion/react-native-gesture-handler#4687 · 3 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
[Android] v3 `ReanimatedSwipeable` takes over a vertical scroll in a React Native list once the finger drifts 10 dp sidewaysForse di nuovo libera @JaydeepAgravat l’ha presa 10 giorni fa e non c’è nessuna pull request aperta. ApertaPlatform: Android
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
software-mansion/react-native-gesture-handler#4670 · 6 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
[Android] A held tap on a Touchable or Pressable in ScrollView does nothing while the keyboard is upForse già presa @m-bert l’ha presa 6 giorni fa. ApertaMissing repro Platform: Android
Difficoltà 4/5 3-5 giorni Idoneità per principianti 50/100
software-mansion/react-native-gesture-handler#4653 · 7 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
[IOS] The "hitslop" attribute used in the packaging component FlatList does not work as expected.ApertaClose when stale Missing repro Platform: iOS
Difficoltà 3/5 1-2 giorni Idoneità per principianti 48/100
software-mansion/react-native-gesture-handler#4649 · 2 commenti ·
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di software-mansion/react-native-gesture-handler
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
pollen-robotics/reachy-mini-desktop-app#341 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
mike-north/AgentMonitors#648 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
vercel-labs/ui#700 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 2 giorni