Skip to content

[CP Staging] Fix selection, keyboard nav, and highlight regressions in group-by split rendering#93540

Merged
JS00001 merged 12 commits into
Expensify:mainfrom
Krishna2323:krishna/fix-sticky-header-remains
Jun 15, 2026
Merged

[CP Staging] Fix selection, keyboard nav, and highlight regressions in group-by split rendering#93540
JS00001 merged 12 commits into
Expensify:mainfrom
Krishna2323:krishna/fix-sticky-header-remains

Conversation

@Krishna2323

@Krishna2323 Krishna2323 commented Jun 14, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

#93526 — Only expanded headers were sticky, so the last one stayed stuck with nothing to push it off. Fix: make all group headers sticky so collapsed ones push the previous header away.

#93527SearchList stopped counting lazy-loaded groupBy groups as selectable, and GroupHeader treated unloaded groups as empty. Fix: restore pre-#92067 selection counting and don’t disable groups that have transactionsQueryJSON.

#93534 — Split rendering added invisible children_container rows between headers, so arrow keys needed two presses. Fix: skip those indices in keyboard nav and clean up border styling so the focus box renders fully.

#93535 — Selection highlight/border only applied to the header after the split. Fix: align selection styling so the full group (header + children) highlights together.

#93536 — New-expense highlight lived on the old single wrapper; after the split only GroupHeader animated. Fix: add useAnimatedHighlightStyle to GroupChildrenContainer so the expanded section highlights too.

Fixed Issues

$ #88926
$ #93526
$ #93527
$ #93534
$ #93535
$ #93536
PROPOSAL:

Tests

Test #93526

  • Precondition:
    • Account has many reports.
  1. Go to staging.new.expensify.com
  2. Go to Spend > Expenses.
  3. Type group-by:from in the search field and search.
  4. Expand the first report.
  5. Scroll down.
  6. Verify the first expanded header is not sticky when the list scrolls and the second group pushes it

Test #93527

  • Precondition:
    • Account has many expenses from different users.
  1. Go to staging.new.expensify.com
  2. Go to Spend > Cash accruals
  3. Click Select all checkbox
  4. Verify it selects all items
  5. Expand the first report
  6. Verify checkboxes for other reports are not disabled

Test #93534

  • Precondition:
    -Account has many expenses from different users.
  1. Go to staging.new.expensify.com
  2. Go to Spend > Cash accruals.
  3. Press keyboard down arrow a few times.
  4. Verify one press on keyboard down arrow navigates to the next report.
  5. Verify blue boxes have complete borders.

Test for #93535

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Go to Spend > Cash accruals.
  5. Expand the report.
  6. Click Select all checkbox.
  7. Verify the entire report group is highlighted.

Test for #93536

  1. Go to new.expensify
  2. Open Spend tab
  3. Go to Cash Accruals and expand a report with an expense that is on an open report
  4. Open the expense and click More > Add expense > Create expense
  5. Add amount and Merchant and click Create
  6. Exit the report view to see the accrual expenses page
  7. Verify newly added expense causes the expanded section and header of the accrual expenses to get highlighted
  • Verify that no errors appear in the JS console

Offline tests

  • Same as tests

QA Steps

  • Same as tests

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
new_expense_highlight_issue.mp4
remaining_bugs.mp4

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323 Krishna2323 changed the title Krishna/fix sticky header remains Fix selection, keyboard nav, and highlight regressions in group-by split rendering Jun 14, 2026
@codecov

codecov Bot commented Jun 14, 2026

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/styles/index.ts 59.37% <ø> (ø)
src/styles/utils/index.ts 52.76% <100.00%> (ø)
...ponents/Search/SearchList/BaseSearchList/index.tsx 0.00% <0.00%> (ø)
...ponents/Search/SearchList/ListItem/GroupHeader.tsx 16.78% <16.66%> (-0.12%) ⬇️
src/hooks/useExpandCollapseAnimation.ts 4.54% <0.00%> (-1.34%) ⬇️
...rch/SearchList/ListItem/GroupChildrenContainer.tsx 0.00% <0.00%> (ø)
src/components/Search/SearchList/index.tsx 51.47% <46.87%> (+2.79%) ⬆️
... and 20 files with indirect coverage changes

@Krishna2323 Krishna2323 marked this pull request as ready for review June 14, 2026 03:03
@Krishna2323 Krishna2323 requested review from a team as code owners June 14, 2026 03:03
@melvin-bot melvin-bot Bot requested review from DylanDylann and JmillsExpensify and removed request for a team June 14, 2026 03:03
@melvin-bot

melvin-bot Bot commented Jun 14, 2026

Copy link
Copy Markdown

@DylanDylann Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@Krishna2323

Copy link
Copy Markdown
Contributor Author

Sorry for the bump @DylanDylann, @ZhenjaHorbach will review this.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 457b83fa21

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/components/Search/SearchList/BaseSearchList/index.tsx Outdated

@JmillsExpensify JmillsExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

… on web

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
Signed-off-by: krishna2323 <belivethatkg@gmail.com>

@JmillsExpensify JmillsExpensify left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

…imation

Signed-off-by: krishna2323 <belivethatkg@gmail.com>
@Krishna2323

Copy link
Copy Markdown
Contributor Author

@codex review

@JS00001 JS00001 changed the title Fix selection, keyboard nav, and highlight regressions in group-by split rendering [CP Staging] Fix selection, keyboard nav, and highlight regressions in group-by split rendering Jun 15, 2026

@JS00001 JS00001 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets go ahead w/ merge here, maybe we can follow up to clean code, but not too important

Comment on lines +331 to +336
for (let i = 0; i < splitData.length; i++) {
const item = splitData.at(i);
if (item && isGroupChildrenContainerItem(item)) {
childrenIndices.push(i);
}
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NAB, prob simpler to do:

Suggested change
for (let i = 0; i < splitData.length; i++) {
const item = splitData.at(i);
if (item && isGroupChildrenContainerItem(item)) {
childrenIndices.push(i);
}
}
for (const [item, index] of splitData.entries()) {
if (isGroupChildrenContainerItem(item)) {
childrenIndices.push(index);
}
}

@JS00001 JS00001 merged commit 04ddc38 into Expensify:main Jun 15, 2026
36 of 38 checks passed
OSBotify pushed a commit that referenced this pull request Jun 15, 2026
…remains

[CP Staging] Fix selection, keyboard nav, and highlight regressions in group-by split rendering

(cherry picked from commit 04ddc38)

(cherry-picked to staging by puneetlath)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Jun 15, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@github-actions

Copy link
Copy Markdown
Contributor

🚧 @JS00001 has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/puneetlath in version: 9.4.7-3 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 No help site changes required.

I reviewed the changes in this PR and they are all internal regression fixes to the group-by split rendering in the Search list — none of them alter customer-facing features, flows, settings, labels, or copy that the help site documents.

Why no docs update is needed

The diff is limited to behavioral/visual bug fixes in the SearchList components:

No new strings, labels, buttons, or user-facing copy were added (the only string-like changes are code symbols and theme color references). Help site articles under App/docs/articles describe customer-facing product behavior and how-tos, not internal list-rendering details like sticky-header behavior, focus-box borders, or keyboard-navigation indexing — so there is nothing to update.

Since no documentation changes are required, I did not create a draft PR.

@Krishna2323, please confirm you agree no help site updates are needed here. If you believe a specific article should be updated, let me know which behavior is customer-facing and I'll draft the changes.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.4.7-4 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/puneetlath in version: 9.4.8-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 failure ❌
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

Help site review — no changes required

I reviewed the changes in this PR against the help site files under App/docs/articles.

Conclusion: No help site updates are required.

Why: This PR is a regression fix for the group-by split-rendering work from #92067. All changes are internal rendering/interaction fixes in src/components/Search/SearchList/, src/hooks/useExpandCollapseAnimation.ts, and src/styles/:

These restore previously-intended behavior. They do not introduce any new feature, setting, tab, button, or label, and they do not change any documented product behavior. Help articles describe how to use features (e.g., searching, grouping, and selecting expenses), and that documented behavior is unchanged by these fixes — so there is nothing to add or correct in the docs, and no draft PR was created.

@Krishna2323, since no help site changes are required, there's no linked help site PR to review. If you believe a specific article should change, let me know which behavior is documented incorrectly and I'll create the draft PR.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/puneetlath in version: 9.4.8-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 Help site review: no changes required.

I reviewed the changes in this PR against the help site articles under docs/articles. No updates are needed, so I did not create a draft docs PR.

Why: This is a bug-fix-only PR. All 8 changed files are internal frontend code — src/components/Search/SearchList/*, src/hooks/useExpandCollapseAnimation.ts, and src/styles/*. The fixes restore intended UI/interaction behavior that regressed from #92067:

None of these introduce, rename, or alter a user-facing feature, setting, tab, or workflow. The group-by search operator that help articles like Use-Search-Operators-to-Filter-and-Analyze.md document is unchanged — its syntax, purpose, and documented behavior are unaffected. These fixes are implementation-level rendering/interaction corrections that the help site does not describe.

@Krishna2323, if you believe a specific article should be updated to reflect behavior changed here, let me know which one and I'll draft the changes.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/puneetlath in version: 9.4.8-3 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

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

Labels

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants