Keep the background expense receipt visible when a wide RHP opens

[KJ21-ENG]

Explanation of Change

MoneyRequestView hides its inline receipt while a wide RHP is open so the receipt is not duplicated next to the wide RHP's left receipt panel. That condition checked wideRHPRouteKeys.length === 0, which is global: once any wide RHP registers, every mounted MoneyRequestView hides its receipt — including instances on screens behind the RHP. After #95131, report hyperlinks can open a wide RHP over a central-pane expense view, so the background expense view loses its receipt box and its content shifts up (the regression from #95131 reported in the linked issue).

This PR scopes the condition to the view's own screen: the receipt is hidden only when the view's route.key is registered in wideRHPRouteKeys (!wideRHPRouteKeys.includes(route.key) instead of wideRHPRouteKeys.length === 0). The MoneyRequestView inside the wide RHP keeps hiding its inline receipt (the wide RHP's left panel shows it), while instances mounted on other screens — such as the central report pane behind the RHP — keep their inline receipt. The small-screen, review-duplicates, and merge-transaction short-circuits are unchanged.

A unit test (tests/ui/MoneyRequestViewReceiptTest.tsx) locks the behavior: it asserts the inline receipt stays visible on a background report screen while another screen owns the wide RHP (this assertion fails against the pre-fix global check), and that the view owning the wide RHP still hides its inline receipt.

cc @blimpich

Fixed Issues

$ #96118
PROPOSAL: #96118 (comment)

Tests

1. Verify that no errors appear in the JS console.
2. On a wide layout, go to a workspace chat and create a manual expense.
3. Open the expense and click Report > Remove from report.
4. Go to the self DM and open the (now unreported) expense so its details page shows in the central pane with the receipt box at the top.
5. Click the report hyperlink in the "moved this expense from …" system message. The linked report opens in the wide expense-report RHP.
6. Verify the expense details page in the background keeps its receipt box and does not shift up while the RHP is open, and still has it after closing the RHP.
7. From the Search tab, open a single-transaction expense report row (wide RHP) and click the expense to open the transaction thread in the RHP. Verify the receipt appears only once — in the RHP's left receipt panel — and the thread body does not show a duplicate inline receipt box, including during the drill-in transition. Then press the RHP back button and verify the revealed report view does not flash a duplicate inline receipt next to its left receipt panel.
8. From Search, open a multi-transaction report (super-wide RHP, table view) and drill into one transaction (opens a wide thread stacked on top). Verify the super-wide report table behind is unaffected — no missing/duplicated receipt and no upward content shift — and returns to normal on back.
9. Open the Review duplicates confirmation page and the Merge expenses confirmation page for a transaction with a receipt. Verify the receipt still renders on each (these paths force-show it), with no wide-RHP interaction removing it.
10. On a narrow layout, open an expense's details page and verify the inline receipt box shows as before.

• Verify that no errors appear in the JS console

Offline tests

This is a render-only condition fix in MoneyRequestView; it does not alter optimistic data, queued requests, or API behavior. Offline check: with the network off, create/scan an expense so its transaction carries a pending receipt, then open a wide RHP over an unrelated report showing that pending receipt on a background screen. Verify the pending receipt stays visible on the background view with the correct grayed offline styling, and going back online settles without the receipt flashing or disappearing.

QA Steps

1. Verify that no errors appear in the JS console.
2. On a wide layout: workspace chat → create an expense → open it → Report > Remove from report → go to self DM → open the expense → click the report hyperlink in the "moved this expense from …" message.
3. Verify the expense details page in the background keeps its receipt box and does not move up when the report RHP opens (regression check for this issue's repro).
4. From Search, open an expense report and click into one of its expenses. Verify the receipt shows once in the RHP's left panel with no duplicate inline receipt in the thread view.
5. From Search, open a multi-transaction report (super-wide RHP) and drill into a transaction; verify the super-wide report table behind is unaffected (no missing/duplicate receipt, no content shift).
6. Open the Review duplicates and Merge expenses confirmation pages for a transaction with a receipt and verify the receipt still renders on each.
7. On a narrow layout, open an expense's details page and verify the receipt box renders as before.

• 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 followed proper code patterns (see Reviewing the code)
  • 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 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)
• 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)
• 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.
• 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

Screen.Recording.2026-07-15.at.1.19.39.PM-compressed.mp4

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
...c/components/ReportActionItem/MoneyRequestView.tsx	74.13% <100.00%> (+0.12%)	⬆️
... and 71 files with indirect coverage changes

[melvin-bot]

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

[cretadn22]

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 proper code patterns were followed (see Reviewing the code)
  • 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 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)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• 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 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 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.
• 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

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

[joekaufmanexpensify]

Good for product