Skip to content

[Due for payment 2026-03-30] [$250] Arrow key navigation not working in Columns selection #78188

Closed

Description

@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.2.85-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #77951
Email or phone of affected tester (no customers): applausetester+tesadb@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Web
App Component: Other

Action Performed:

  1. Navigate to Reports → Columns.
  2. Try using the Up and Down arrow keys to select column options.

Expected Result:

The Up and Down arrow keys should allow keyboard navigation

Actual Result:

The Up and Down arrow keys do not move the selection or highlight any column options.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7034096_1766195053671.2025-12-20_02-34-10.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022003081758600762647
  • Upwork Job ID: 2003081758600762647
  • Last Price Increase: 2026-01-05
  • Automatic offers:
    • aimane-chnaif | Reviewer | 110002644
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Dec 20, 2025
  2. melvin-bot commented on Dec 20, 2025

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (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.

  3. melvin-bot commented on Dec 20, 2025

    @melvin-bot

    Triggered auto assignment to @chuckdries (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Dec 20, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 20, 2025

    @github-actions
    Contributor

    👋 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.
  6. 67 remaining items

  7. TaduJR commented on Mar 31, 2026

    @TaduJR
    Contributor

    Offer Accepted @mallenexpensify

    Thanks!

  8. mallenexpensify commented on Apr 1, 2026

    @mallenexpensify
    Contributor

    @TaduJR paid, summary updated above. Thx.

  9. mallenexpensify commented on Apr 1, 2026

    @mallenexpensify
    Contributor

    ugggh, payment should be reduced by 50% cuz the regression, reopening.
    @aimane-chnaif @TaduJR post and provide reasoning, otherwise I'll request the refund in a day or two.

  10. aimane-chnaif commented on Apr 1, 2026

    @aimane-chnaif
    Contributor

    It's technically not a regression but missing edge case. (this didn't work in production)
    We both thought that was expected.

    Actually, we could have asked to increase bounty for PR complexity.

    @JS00001 what do you think?

  11. JS00001 commented on Apr 1, 2026

    @JS00001
    Contributor

    I think we should stick with the $250 payout here, which should account for the increased complexity, but minor regression as well. Does that work?

  12. TaduJR commented on Apr 1, 2026

    @TaduJR
    Contributor

    BTW @JS00001

    We also handle accessibility related issues here

    For example there was double focus when navigating with tab on the checkbox

  13. mallenexpensify commented on Apr 6, 2026

    @mallenexpensify
    Contributor

    We also handle accessibility related issues here

    Was this a separate PR?

    I'm planning to leave the price the same but will leave it open for a min.

  14. TaduJR commented on Apr 6, 2026

    @TaduJR
    Contributor

    Was this a separate PR?

    It's on the same main PR.

  15. TaduJR commented on Apr 7, 2026

    @TaduJR
    Contributor

    We can close this one right @mallenexpensify?

  16. mallenexpensify commented on Apr 7, 2026

    @mallenexpensify
    Contributor

    Closing, comment/reopen if you disagree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions