Touches don’t work on absolutely positioned child when it goes outside parent’s bounds (Android only)
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 38/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Estagnada
- Stack de tecnologia
- android, react-native
- Domínio
- mobile
Direção de pesquisa
Comece executando o reproducer Snack vinculado no Android e compare seu comportamento de toque com o do iOS, usando como ponto de entrada o filho posicionado absolutamente que contém um Switch ou WebView. Rastreie o tratamento de toque do Android para filhos que se estendem além dos limites de um pai. Considera-se concluído quando a parte fora do pai também recebe interação, sem alterar o comportamento dentro dele.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Description
<GestureHandlerRootView style={styles.root}>
<GestureDetector gesture={composedGesture}>
<Animated.View style={styles.canvasWrapper}>
// the red box
<Animated.View style={[styles.canvasTransform, canvasAnimatedStyle]}>
<Animated.View
style={{
position: 'absolute',
left: 300,
top: 0,
}}
collapsable={false}>
<YoutubePlayer height={300} width={400} videoId={'HzL65tTeANs'} play={true} />
</Animated.View>
</Animated.View>
<Animated.View style={focalPointStyle} pointerEvents="none" />
</Animated.View>
</GestureDetector>
</GestureHandlerRootView>
I have a parent <Animated.View> (the red box in my demo). Inside it, I have another <Animated.View> that’s absolutely positioned and contains a react-native-youtube-iframe player
When the absolutely positioned animated.view is inside the red box(the parent), everything works fine. I can play pause and interact with the video
But once it goes outside the parent bounds, the video stops receiving touches.
as you can see from my demo video that only the part of the video inside the red box receives touch events
Note: the problem is not related to react-native-youtube-iframe i tested it with a regular React Native component like <Switch /> and the same behavior occurs with only android
Steps to reproduce
1- Create a parent <Animated.View> that acts as a container
2- Inside it, create another <Animated.View> with position: 'absolute' and place it so that part of it goes outside the parent’s bounds.
3- Inside the absolutely positioned animated.view, render for example <Switch /> or even a WebView.
4- Run the app on Android.
5- Try interacting with the <Switch />:
When the absolutely positioned animated.view and the switch are inside the parent's layout, the switch works fine.
When you move the absolutely positioned animated.view and the switch are outside the parent’s layout. the switch doesn't work
6- Run the same code on iOS. everything works fine
React Native Version
0.81.4
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: Windows 11 10.0.26100
CPU: (24) x64 Intel(R) Core(TM) i7-14650HX
Memory: 2.45 GB / 15.71 GB
Binaries:
Node:
version: 22.17.0
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 1.22.22
path: C:\Users\LEGION\AppData\Roaming\npm\yarn.CMD
npm:
version: 10.9.2
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-251.26094.121.2513.14007798
Visual Studio: Not Found
Languages:
Java:
version: 17.0.16
path: C:\Program Files\Microsoft\jdk-17.0.16.8-hotspot\bin\javac.EXE
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 19.1.0
wanted: 19.1.0
react-native:
installed: 0.81.4
wanted: 0.81.4
react-native-windows: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Stacktrace or Logs
The issue is only related to touch behavior on Android (no crash).
MANDATORY Reproducer
https://snack.expo.dev/@khldon123/repro?platform=web
Screenshots and Videos
https://github.com/user-attachments/assets/1146f77e-95d4-4960-85ba-f538cb73ec36
- Linguagem predominante
- C++
- Estrelas
- 127k
- Forks
- 25.3k
- Merge médio
- 1d 23h
- PRs com merge (30d)
- 4
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de react/react-native
-
Needs: Triage :mag:
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
react/react-native#58565 · 1 comentário · 2 reações ·
-
Needs: Author Feedback Needs: Repro
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
react/react-native#58555 · 4 comentários · 1 reação ·
-
Needs: Attention Needs: Repro
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
react/react-native#58526 · 2 comentários ·
-
Needs: Author Feedback Needs: Repro
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
react/react-native#58448 · 1 comentário ·
-
Needs: Attention Needs: Repro
Dificuldade 2/5 Meio dia Facilidade para iniciantes 82/100
react/react-native#58441 · 2 comentários ·
Todas as issues de react/react-native
Issues semelhantes
-
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 92/100
autowarefoundation/autoware_universe#13413 ·
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
-
automated-analysis bug memory-safety
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
gazebosim/gz-sensors#662 · 1 comentário ·