fix: prevent BridgeView from blocking zero-state trending scroll#28103
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection: Performance Test Selection: |
|
|
✅ E2E Fixture Validation — Schema is up to date |



Description
Bridge zero-state scrolling could get stuck when a drag started from the amount area above trending tokens because the outer
BridgeViewwrapper always claimed the initial responder.This change keeps the existing blur-and-close behavior for other bridge states, but lets the scroll view own the gesture when zero-state trending content is visible so users can scroll naturally into the trending section.
Changelog
CHANGELOG entry: Fixed bridge zero-state trending scrolling when dragging from the amount area
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
N/A
After
N/A
Pre-merge author checklist
Pre-merge reviewer checklist
Note
Low Risk
Low risk UI gesture-handling change limited to the Bridge zero-state when the trending-tokens flag is enabled; main risk is unintended responder behavior differences in that specific mode.
Overview
Prevents
BridgeView’s outer wrapper from always claiming touch responder events by makingonStartShouldSetResponderconditional.When the bridge is in zero-state and trending tokens are enabled, the wrapper no longer intercepts the initial gesture so the inner
ScrollViewcan scroll normally; all other modes keep the existing tap-to-blur input and close keypad behavior.Written by Cursor Bugbot for commit 61a894d. This will update automatically on new commits. Configure here.