[Due for payment 2026-03-11] Distance - Waypoints auto change to previous waypoints after pressing Tab

[mitarachim]

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.6-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79793
Email or phone of affected tester (no customers): osidjoisdjnojdisjid@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Click + > Track distance > Map.
3. Enter A and B waypoint.
4. Press Tab until it reaches Start waypoint.
5. Press keyboard space, down arrow, and Enter.
6. Press Enter again.
7. Close the RHP.
8. Click + > Track distance > Map.
9. Enter A and B waypoint.
10. Press Tab.

Expected Result:

A and B waypoint will not change order.

Actual Result:

A and B waypoint change to B and A.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7055114_1769039001875.3.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @mallenexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[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: #79793 - "feat: implement keyboard reordering for DraggableList" by @MobileMage (High confidence)
Related Issues: None

Recommendation: REVERT

PR #79793 introduced keyboard-accessible reordering functionality to the DraggableList component, but it appears to be causing unintended waypoint reordering behavior when users navigate with the Tab key.

Labels: Keeping DeployBlockerCash (App deploy is blocked). Removing DeployBlocker (this is a frontend bug in the App, not a backend issue).

📋 Detailed Analysis

Evidence

1. Timing: PR feat: implement keyboard reordering for DraggableList #79793 was merged on 2026-01-20 at 21:47 UTC and is included in staging deploy 9.3.6-0
2. Code changes: The PR added KeyboardSensor with sortableKeyboardCoordinates to DraggableList
3. Affected component: DraggableList is used by distance waypoint screens (IOURequestStepDistance.tsx)
4. Reproduction: Issue only appears on staging (where PR feat: implement keyboard reordering for DraggableList #79793 is deployed) and affects the keyboard navigation flow
5. Auto-detection: Melvin-bot correctly identified this PR as the likely cause

Verification

• Affected files: src/components/DraggableList/index.tsx (modified by PR feat: implement keyboard reordering for DraggableList #79793)
• Usage in waypoints: Both IOURequestStepDistance.tsx and IOURequestStepDistanceMap.tsx use DraggableList with waypoint data
• Bug manifestation: After using keyboard drag-drop in one distance request, opening a new distance request and pressing Tab causes waypoints to swap order unexpectedly

Root Cause

The KeyboardSensor implementation appears to have a state persistence issue where keyboard navigation (Tab) can trigger unintended reordering actions, possibly due to:

• Sensor state not being properly reset between component instances
• Tab key interaction with the keyboard sensor activation
• Focus management conflict between Tab navigation and drag-drop keyboard controls

The intended behavior was to enable Space + Arrow keys for reordering (accessibility improvement), but the implementation has an unintended side effect where normal Tab navigation triggers waypoint swapping.