Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.98k stars 2.98k forks source link

Search - Search field is not auto focused when opened #55119

Closed IuliiaHerets closed 1 week ago

IuliiaHerets commented 2 weeks ago

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: v9.0.84-0 Reproducible in staging?: Yes Reproducible in production?: No Email or phone of affected tester (no customers): applausetester+bg@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Windows / Chrome App Component: Search

Action Performed:

  1. Go to https://staging.new.expensify.com/
  2. Login to any account
  3. Click on the search icon at the top

Expected Result:

The Search field is auto-focused

Actual Result:

The search field is not auto-focused

Workaround:

Unknown

Platforms:

Screenshots/Videos

https://github.com/user-attachments/assets/25a93f79-fee4-4f4c-a103-adc589222967

View all open jobs on GitHub

melvin-bot[bot] commented 2 weeks ago

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

melvin-bot[bot] commented 2 weeks ago

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

melvin-bot[bot] commented 2 weeks ago

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

github-actions[bot] commented 2 weeks ago

:wave: 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.
ishpaul777 commented 1 week ago

this is coming from https://github.com/Expensify/App/pull/54276

reverting it solves the issue

https://github.com/user-attachments/assets/4ceb95d9-cd54-453f-adca-79ad5048db68

mountiny commented 1 week ago

Gonna move this ahead