Skip to content

Skip Wide RHP state in EditableCell outside the RHP - #104834

Merged
rlinoz merged 5 commits into
Expensify:mainfrom
callstack-internal:editable-cell-wide-rhp-state
Oct 26, 2026
Merged

rlinoz merged 5 commits into
Expensify:mainfrom
callstack-internal:editable-cell-wide-rhp-state

Conversation

@TMisiukiewicz

@TMisiukiewicz TMisiukiewicz commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Every editable cell in the expense table (amount, tag, category and similar cells in Spend and in the expense report table) subscribed to the Wide RHP state. That state changes each time a side panel opens, closes or changes width. So every cell in every row re-rendered whenever the right-hand panel moved, even when the table was in the main pane and the panel had nothing to do with it.

Now a cell only reads the Wide RHP state when it is actually shown inside the right-hand panel. Cells in the main pane skip that read and no longer re-render when the panel opens or closes. Whether a cell can be edited stays the same as before:

  • In the main pane on a wide screen, cells are editable.
  • Inside a Wide or Super Wide right-hand panel, cells are editable.
  • Inside a normal (narrow) right-hand panel, or on a narrow screen, cells are not editable.
  • On iOS and Android the Wide RHP never shows, so this check always returns "not in a Wide RHP".

Fixed Issues

$ #104858
PROPOSAL:

Tests

  1. On a wide screen (web or desktop), go to Spend > Expenses with a few expenses that you can edit.
  2. Hover over the amount, category or tag cell of an expense and verify the edit pencil shows. Click it and verify you can edit the value inline.
  3. Open an expense report from the list so it shows in the wide right-hand panel. Hover over a cell in the report's expense table and verify you can still edit it inline.
  4. Open a screen that uses a normal (narrow) right-hand panel and shows the expense table, if any. Verify the cells there are not editable inline.
  5. Close the right-hand panel and verify the cells in Spend are still editable.
  6. Shrink the browser window to a narrow width and verify the cells are no longer editable inline.
  7. On iOS and Android, open Spend and an expense report and verify cells are not editable inline, same as before.
  8. Optional: with React DevTools "Highlight updates" on, open and close an expense report from Spend and verify the table rows in the main pane no longer flash.
  • Verify that no errors appear in the JS console

Offline tests

Same as tests, but with the network connection turned off. Verify the app behaves the same and no errors appear.

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
  • 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 any copy / text that was added to the app 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • 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)
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • 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

🤖 Generated with Claude Code

@codecov

codecov Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/components/EditableCell/EditableCell.tsx 91.48% <100.00%> (+0.37%) ⬆️
src/components/WideRHPContextProvider/index.tsx 0.00% <ø> (ø)
...hooks/useResponsiveLayoutOnWideRHP/index.native.ts 100.00% <100.00%> (ø)
src/hooks/useResponsiveLayoutOnWideRHP/index.ts 42.85% <100.00%> (+42.85%) ⬆️
... and 46 files with indirect coverage changes

@BartekObudzinski

Copy link
Copy Markdown
Contributor

@MelvinBot please update an issue in pr description to this one #104858

@MelvinBot

Copy link
Copy Markdown
Contributor

I updated the Fixed Issues section of the PR description. It now links Performance: Avoid Wide RHP subscriptions in expense table cells outside the RHP.


view run

@BartekObudzinski

Copy link
Copy Markdown
Contributor

I tested and updated the PR, @MelvinBot could you mark this pr ready to review

@MelvinBot
MelvinBot marked this pull request as ready for review October 26, 2026 12:13
@MelvinBot
MelvinBot requested review from a team as code owners October 26, 2026 12:13
@MelvinBot

Copy link
Copy Markdown
Contributor

This PR is now marked as ready for review.


view run

@melvin-bot
melvin-bot Bot requested review from brunovjk and removed request for a team October 26, 2026 12:13
@melvin-bot

melvin-bot Bot commented Oct 26, 2026

Copy link
Copy Markdown

@brunovjk 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]

@melvin-bot
melvin-bot Bot requested review from trjExpensify and removed request for a team October 26, 2026 12:13
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-26T12:28:46.062456Z eff7459 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@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: eff7459c40

ℹ️ 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".

const isDisplayedInWideRHP = useIsDisplayedInWideRHP(isInNarrowPaneModal);
const [isEditIconFocused, setIsEditIconFocused] = useState(false);
const isEditable = isLargeScreenWidth && !shouldUseNarrowLayout;
const isEditable = isLargeScreenWidth && (!shouldUseNarrowLayout || isDisplayedInWideRHP);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve the small-screen guard for Wide RHP routes

On an mWeb phone in landscape whose viewport exceeds the large-screen breakpoint, useResponsiveLayout() reports both isLargeScreenWidth and shouldUseNarrowLayout as true. SearchMoneyRequestReportPage still calls useRHPWidth() at src/pages/Search/SearchMoneyRequestReportPage.tsx:196, so its route can also make isDisplayedInWideRHP true; this OR then enables inline editing even though the screen is using the narrow layout. The previous wrapper explicitly required !isSmallScreenWidth before treating a registered route as wide, so this decision also needs that guard.

Useful? React with 👍 / 👎.

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.

Good catch on the missing small-screen check, though it doesn't enable editing there: the report rows fall back to the narrow row, which passes no canEdit, so the only effect was the cell padding. Moved the check into useIsDisplayedInWideRHP anyway so behavior matches the old wrapper exactly, and added a test.

@brunovjk

brunovjk commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified any copy / text that was added to the app 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)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 the PR adds or modifies the UI:
    • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
    • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
    • I verified all new/changed elements have meaningful accessible names and roles.
    • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
104834_android_native.mov
Android: mWeb Chrome
104834_android_web.mov
iOS: HybridApp
104834_ios_native.mov
iOS: mWeb Safari
104834_ios_native.mov
MacOS: Chrome / Safari
104834_web_chrome.mov

@brunovjk brunovjk 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

@melvin-bot
melvin-bot Bot requested a review from rlinoz October 26, 2026 16:23
@rlinoz
rlinoz merged commit a4394d7 into Expensify:main Oct 26, 2026
35 of 38 checks passed
@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

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

@github-actions

Copy link
Copy Markdown
Contributor

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/rlinoz in version: 9.5.21-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update is needed: this PR only stops expense table cells from re-rendering when the right-hand panel changes, and inline editing works exactly as before.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/rlinoz in version: 9.5.23-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

No help site update is needed: this PR only stops expense table cells from re-rendering when the right-hand panel changes, and inline editing works exactly as before.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.5.23-3 🚀

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

Bundle Size Analysis (Sentry):

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants