[$250] Web - Distance - Unable to reorder waypoints using keyboard

[lanitochka17]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.27-5
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #82500
Email or phone of affected tester (no customers): sjdsoijsoidjsndoinjsdoi@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Open FAB > Track distance > Map.
3. Enter Start and Stop waypoint.
4. Tab to a waypoint.
5. Press space on the keyboard.
6. Press down arrow on the keyboard.

Expected Result:

In Step 5, after pressing space on a waypoint, it will be picked up so that user can move it down with keyboard (according to #79793).

Actual Result:

In Step 5, after pressing space on a waypoint, waypoint editor opens.
User cannot reorder waypoints using keyboard.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7092083_1772466319793.12.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @abzokhattab

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022031094593402003287
• Upwork Job ID: 2031094593402003287
• Last Price Increase: 2026-03-09

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #82500

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #82500 - "Add keyboard navigation support for autocomplete result rows" by @MobileMage (High confidence)
Related Issues: None directly linked, but PR #80261 appears to contain additional keyboard handling fixes

Recommendation: REVERT

PR #82500 should be reverted from staging. The PR added keyboard navigation support to google-places-autocomplete rows, which appears to have introduced a conflict with the waypoint reordering keyboard shortcuts implemented in PR #79793.

Note: PR #80261 ("fix: resolve keyboard reordering edge cases in DraggableList") was merged shortly after #82500 and may contain relevant fixes. It should be included when re-landing #82500.

Labels: Removing DeployBlockerCash - this issue does not block the App deploy as it was caught during regression testing and only affects staging.

Detailed Analysis

Evidence

1. The issue explicitly links to PR Add keyboard navigation support for autocomplete result rows #82500 in the regression testing field
2. The bug is reproducible on staging (v9.3.27-5) which includes PR Add keyboard navigation support for autocomplete result rows #82500
3. The bug is NOT reproducible on production, which does not include PR Add keyboard navigation support for autocomplete result rows #82500
4. PR Add keyboard navigation support for autocomplete result rows #82500 was merged on 2026-02-27 at 14:21:43Z and is included in the staging deploy checklist

Verification

PR #82500 changed files:

• patches/react-native-google-places-autocomplete/details.md
• patches/react-native-google-places-autocomplete/react-native-google-places-autocomplete+2.5.6+002+keyboard-navigation.patch

The patch adds keyboard accessibility to autocomplete rows including:

• tabIndex={0} to make rows focusable
• accessibilityRole="button"
• Space key handler with preventDefault()

Waypoint reordering (from PR #79793):

• Uses DraggableList component with @dnd-kit KeyboardSensor
• Space key is configured to start/end drag operations
• Waypoint items use MenuItem component with role="button"

Root Cause

While the exact interaction mechanism is complex, the evidence strongly points to PR #82500 introducing a conflict with keyboard event handling that prevents waypoint reordering via Space key. The timing of PR #80261 (merged 2 hours after #82500 on the same day) with fixes for "keyboard reordering edge cases" suggests the issue was identified and fixed, but #80261 is not yet on staging.