react / react/react-native

Pressables don't prevent touches being forwarded to OS

未关闭
#56,061 2 条评论 15 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

Needs: Triage :mag: p: Callstack Partner
主要语言
C++
星标
127k
派生
25.3k
平均合并
1 天 23 小时
30 天内合并 PR
4

描述

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
  1. Install the app on iPad simulator with yarn ios
  2. Scroll the scrollview so it's not at the top
  3. Click on the button in the header
  4. 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

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

先从 https://github.com/satya164/iPadTouchableRepro 中的必需 reproducer 开始,复现 issue 中描述的 iPadOS 行为,然后跟踪 Pressable 的 iOS 触摸处理。未指定源文件或测试;完成标准是激活 Pressable 后不再同时触发 iPadOS 的滚动到顶部行为,同时 native controls 不受影响。

由索引模型根据 Issue 内容生成。

评估

技术栈
react-native
领域
mobile
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
冷清
描述清晰度
基本清楚
新手友好度
45/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。