Pressables don't prevent touches being forwarded to OS
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- C++
- Estrellas
- 127k
- Forks
- 25.3k
- Merge medio
- 1 d 23 h
- PR fusionados (30 d)
- 4
Descripción
Description
React Native pressables don't seem to prevent the touches from being forwarded to the OS. This results in unexpected behavior in some situations.
e.g. on iPadOS, there is a large area at the top of the screen that can be tapped to scroll to the top. This area usually covers a similar height to the header bar. If headers have buttons that use pressables, the pressable handles the action, but iPadOS also handles the touch and scrolls any scrollview in the screen to the top.
This does not happen when using a native control (e.g., with UIControl), and only happens with React Native's Pressable. It is very common to add custom buttons to the header (even when using native stack and native header), many people also use custom headers. So the unexpected scroll to top results in a bad UX.
I'm not aware of a way to prevent this behavior right now.
Steps to reproduce
- Install the app on iPad simulator with
yarn ios - Scroll the scrollview so it's not at the top
- Click on the button in the header
- Observe that the button also scrolls the scrollview to the top
React Native Version
0.84.1
Affected Platforms
Runtime - iOS
Output of npx @react-native-community/cli info
System:
OS: macOS 26.3
CPU: (14) arm64 Apple M4 Pro
Memory: 119.75 MB / 48.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 24.13.0
path: /Users/satya/.local/state/fnm_multishells/2979_1773239105373/bin/node
Yarn:
version: 1.22.22
path: /opt/homebrew/bin/yarn
npm:
version: 11.6.2
path: /Users/satya/.local/state/fnm_multishells/2979_1773239105373/bin/npm
Watchman:
version: 2025.10.13.00
path: /run/current-system/sw/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 25.2
- iOS 26.2
- macOS 26.2
- tvOS 26.2
- visionOS 26.2
- watchOS 26.2
Android SDK:
API Levels:
- "28"
- "29"
- "30"
- "31"
- "32"
- "33"
- "35"
- "36"
- "36"
Build Tools:
- 28.0.3
- 29.0.2
- 30.0.2
- 30.0.3
- 31.0.0
- 32.0.0
- 33.0.0
- 33.0.1
- 34.0.0
- 35.0.0
- 35.0.0
- 36.0.0
System Images:
- android-24 | Google APIs ARM 64 v8a
- android-34 | Google APIs ARM 64 v8a
- android-36.1 | Pre-Release 16 KB Page Size Google APIs ARM 64 v8a
- android-36 | Google Play ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2025.3 AI-253.30387.90.2532.14935130
Xcode:
version: 26.2/17C52
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.8.1
path: /opt/homebrew/opt/sdkman-cli/libexec/candidates/java/current/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 20.1.0
wanted: 20.1.0
react:
installed: 19.2.3
wanted: 19.2.3
react-native:
installed: 0.84.1
wanted: 0.84.1
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
Stacktrace or Logs
NA
MANDATORY Reproducer
https://github.com/satya164/iPadTouchableRepro
Screenshots and Videos
https://github.com/user-attachments/assets/d81dcc82-ddf7-4c0b-82f1-f4bdb70ad798
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.
Línea de trabajo
Comienza con el reproductor obligatorio en https://github.com/satya164/iPadTouchableRepro y reproduce el comportamiento de iPadOS descrito en el issue; después, sigue el manejo de toques de iOS de Pressable. No se indica ningún archivo de origen ni ninguna prueba; se considera terminado cuando activar un Pressable ya no desencadena también el comportamiento de desplazamiento al inicio de iPadOS, mientras los controles nativos no se ven afectados.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- react-native
- Área
- mobile
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100