[HOLD for payment 2024-12-12] [HOLD for payment 2024-12-11] Search - Search dropdown button is green in wide layout and gray in narrow layout

[IuliiaHerets]

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.0.70-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): applausetester+kh1311020@applause.expensifail.com
Issue reported by: Applause Internal Team

Action Performed:

1. On web, go to staging.new.expensify.com
2. Go to Search.
3. Select expense via checkbox.
4. Note that the dropdown button is green.
5. Change it to narrow layout (mweb, Android and iOS).
6. Now the dropdown button is gray.

Expected Result:

There should be consistency in dropdown button color in wide and narrow layout.

Actual Result:

The dropdown button color is green in wide layout, and gray in narrow layout.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6682508_1733186901993.iOS.mp4

Bug6682508_1733186901945.web.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @zanyrenney

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @zanyrenney (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]

💬 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.

[IuliiaHerets]

Production

Screen.Recording.2024-12-03.at.8.02.30.AM.mov

[shubham1206agra]

Offending PR #53124

[hungvu193]

Taking a look 👀