[Due for payment 2026-04-30] [Due for payment 2026-04-28] Reports - User will need to scroll the list to view one card result from card quick filter

[jponikarchuk]

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.60-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: #86297
Email or phone of affected tester (no customers): applausetester+khcategory19@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Search

Action Performed:

Precondition:

• Workspace is set up with Expensify card feature.
• User has assigned at least 16 cards to any member.

1. Go to staging.new.expensify.com
2. Go to Reports > Expenses.
3. Click Filters.
4. Click Card.
5. Select any card > Save > View results.
6. Click Card quick filter.
7. Enter card number that will provide one result.

Expected Result:

User will not need to scroll the list to view one card result from card quick filter.

Actual Result:

User will need to scroll the list to view one card result from card quick filter.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @bernhardoj

[melvin-bot]

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

[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: #86297 Revamp search page actions bar by @bernhardoj (High confidence) - Recommendation: REVERT - PR 86297 restructured the search page header layout causing results list to be pushed down, requiring scroll to see results. Fix requires App repo changes. Assigned: @bernhardoj (PR author), @JS00001, @aimane-chnaif, @luacmartins (approving reviewers). Labels: DeployBlockerCash kept (frontend bug). Root Cause: filter chips moved inline with search input in flexWrap container plus new action buttons row, making header taller and pushing results list down. Key files: src/components/Search/SearchPageHeader/SearchActionsBarWide.tsx, src/components/Search/SearchPageHeader/SearchFiltersBarWide.tsx, src/styles/index.ts

[MelvinBot]

Proposal

What is the root cause of that problem?

getSelectionListPopoverHeight in src/styles/index.ts:6273-6290 calculates a fixed height for filter dropdown popups using optionRowHeightCompact (52px) per item. However, CardListItem renders with optionRowHeight (64px) via the optionRow style. This 12px-per-item underestimate, combined with section headers (e.g. "Individual Cards", "Card Feeds") not being counted at all, means the container is always too short — forcing a scrollbar even for a single result.

What changes do you think we should make in order to solve the problem?

CardSelectPopup (src/components/Search/FilterDropdowns/CardSelectPopup.tsx:191) should use getCommonSelectionListPopoverHeight (line 6292) instead of getSelectionListPopoverHeight, passing variables.optionRowHeight (64) as the itemHeight parameter to match the actual rendered height of card items. Section header height should also be accounted for by adding the count of non-empty titled sections to the item count calculation.

What alternative solutions did you explore? (Optional)

Changing the fixed height in getSelectionListPopoverHeight to maxHeight would let the container shrink to fit, but the existing comment (line 6284) notes native platforms don't support maxHeight as expected. Using getCommonSelectionListPopoverHeight with the correct item height is the more targeted fix.

Investigation details

• Height estimation (src/styles/index.ts:6280): ESTIMATED_LIST_HEIGHT = itemCount * variables.optionRowHeightCompact uses 52px per item
• Actual card item height (src/styles/index.ts:1931-1935): optionRow style sets minHeight: variables.optionRowHeight which is 64px (src/styles/variables.ts:121)
• CardSelectPopup call site (src/components/Search/FilterDropdowns/CardSelectPopup.tsx:191-196): passes sections.flatMap((section) => section.data).length — counts data items only, not section headers
• Section headers (src/components/SelectionList/hooks/useFlattenedSections.ts:55): rendered for non-empty sections with titles, consuming additional vertical space not included in the estimate
• There is already a getCommonSelectionListPopoverHeight (line 6292) that accepts a custom itemHeight parameter — this is the appropriate function for items that don't match optionRowHeightCompact

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[JS00001]

@bernhardoj are you able to fix this to CP?