Touches don’t work on absolutely positioned child when it goes outside parent’s bounds (Android only)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 38/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- android, react-native
- Área
- mobile
Línea de trabajo
Comienza ejecutando el reproductor Snack enlazado en Android y compara su comportamiento táctil con iOS, usando como punto de entrada el hijo posicionado de forma absoluta que contiene un Switch o WebView. Rastrea el manejo táctil de Android para los hijos que se extienden más allá de los límites de su padre. Se considera terminado cuando la parte situada fuera del padre también recibe interacción sin cambiar el comportamiento dentro de él.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- C++
- Estrellas
- 127k
- Forks
- 25.3k
- Merge medio
- 1 d 23 h
- PR fusionados (30 d)
- 4
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de react/react-native
-
Needs: Triage :mag:
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
react/react-native#58565 · 1 comentario · 2 reacciones ·
-
Needs: Author Feedback Needs: Repro
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
react/react-native#58555 · 4 comentarios · 1 reacción ·
-
Needs: Attention Needs: Repro
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
react/react-native#58526 · 2 comentarios ·
-
Needs: Author Feedback Needs: Repro
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
react/react-native#58448 · 1 comentario ·
-
Needs: Attention Needs: Repro
Dificultad 2/5 Medio día Aptitud para principiantes 82/100
react/react-native#58441 · 2 comentarios ·
Todos los issues de react/react-native
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
gazebosim/gz-sensors#662 · 1 comentario ·
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
comp-datalake
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
ClickHouse/ClickHouse#121222 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
LadybirdBrowser/ladybird#12123 ·