feat: show full distance e-receipt on hover for map distance requests by WojtekBoman · Pull Request #92525 · Expensify/App

WojtekBoman · 2026-06-03T14:33:53Z

Explanation of Change

On hover over a map distance expense receipt, overlay the full distance e-receipt (map + amount + waypoints) scaled with object-fit:contain to fit the fixed receipt box without resizing it, matching Expensify Classic. Adds the HoveredDistanceEReceipt component, wires it into MoneyRequestReceiptView (gated on isMapDistanceRequest && hovered), and a new eReceiptHoverFill style.

Fixed Issues

$ #90793 (comment)
PROPOSAL:

Tests

Open a report and create (or open) a map-based distance expense (created via the map/route flow, not a manually entered distance).
Open the report/transaction so the receipt thumbnail (the map preview) is visible in the receipt box.
Hover the mouse over the receipt box.
Verify that the full distance e-receipt (map + amount + waypoints) appears as an overlay, scaled down to fit entirely inside the receipt box.
Verify that the receipt box does not change size or shift while hovering, and that there is no white gap around the scaled card (the surrounding fill matches the card background).
Move the mouse off the receipt and verify the overlay disappears, returning to the plain map thumbnail.
Repeat for a manually entered distance expense and verify the hover overlay does not appear.

Verify that no errors appear in the JS console

Offline tests

Go offline.
Open a report containing a map distance expense.
Hover over the receipt box and verify the full distance e-receipt overlay still renders from cached transaction data (map, amount, waypoints).

QA Steps

Same as tests.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

codecov · 2026-06-03T14:46:37Z

Codecov Report

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

Files with missing lines	Coverage Δ
src/styles/index.ts	`59.06% <ø> (ø)`
...nents/ReportActionItem/MoneyRequestReceiptView.tsx	`69.95% <92.30%> (+0.24%)`	⬆️
...nents/ReportActionItem/HoveredDistanceEReceipt.tsx	`6.66% <6.66%> (ø)`
... and 524 files with indirect coverage changes

github-actions · 2026-06-03T14:49:00Z

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

shawnborton · 2026-06-03T15:14:15Z

Works great on my end :thu

shawnborton · 2026-06-03T15:14:26Z

Works great on my end 👍 nice work!

melvin-bot · 2026-06-03T15:17:45Z

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

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 863ed13207

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

Copilot

Pull request overview

This PR adds a desktop hover overlay for map-based distance receipts so reviewers can see the full distance e-receipt (map + amount + waypoints) inside the fixed receipt box (scaled to “contain”), matching Expensify Classic behavior.

Changes:

Introduces HoveredDistanceEReceipt to render a scaled, contained full distance e-receipt overlay.
Wires the overlay into MoneyRequestReceiptView behind isMapDistanceRequest && hovered.
Adds an eReceiptHoverFill style to ensure the overlay background matches the e-receipt panel (no visible gap around the scaled card).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
src/styles/index.ts	Adds a background fill style used by the hover overlay to match the distance e-receipt background.
src/components/ReportActionItem/MoneyRequestReceiptView.tsx	Renders the hover overlay for map distance receipts and introduces `isMapDistanceRequest` gating.
src/components/ReportActionItem/HoveredDistanceEReceipt.tsx	New component that measures the receipt box + e-receipt and scales the overlay to fit (“contain”).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

QichenZhu · 2026-06-04T10:53:19Z

    const isDistanceRequest = isDistanceRequestTransactionUtils(transaction);
+    const isMapDistanceRequest = !!transaction && isDistanceRequest && !isManualDistanceRequest(transaction);


This comment is genuine.

Steps to reproduce:

Create a map distance expense.

Create a manual distance expense.

Merge the 2nd expense into the 1st expense and select the 1st expense as the merchant to keep.

Expected result:

E-receipt displays on hover.

Actual result:

Only the map enlarges on hover.

Screen.Recording.2026-06-04.at.10.55.21.PM.mov

Now it should work fine, I've added here logic checking if the transaction has defined waypoints, if so, we'll display an e-receipt

WojtekBoman · 2026-06-08T09:20:07Z

@@ -623,23 +623,28 @@ function MoneyRequestReceiptView({
                                    isEnabled={canZoomReceipt}


E-receipts zoom on hover is intended

trjExpensify

Looks good to me too 👍

QichenZhu

Clicking the thumbnail doesn't open the receipt modal. Is this intentional?

92525.mov

dannymcclain · 2026-06-04T12:21:04Z

Clicking the thumbnail doesn't open the receipt modal. Is this intentional?

No it should open the receipt modal. But the weird thing is the first time I clicked it, it worked as expected, but then after that first time, clicking did nothing.

…t clicks

WojtekBoman · 2026-06-08T09:33:26Z

@QichenZhu @Expensify/design All comments have been resolved :) Feel free to generate new builds!

github-actions · 2026-06-08T09:40:08Z

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

QichenZhu · 2026-06-08T12:53:06Z

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
Allow receipt zooming where customers can roll over receipts with the mouse to zoom in #90793 (comment)
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
https://expensify.slack.com/archives/C049HHMV9SM/p1778663561704459
I verified proper code patterns were followed (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
- 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 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)
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
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- 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
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- 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 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 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.
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

Screen.Recording.2026-06-09.at.12.37.02.AM.mov

Android: mWeb Chrome

Screen.Recording.2026-06-09.at.12.39.18.AM.mov

iOS: HybridApp

Simulator.Screen.Recording.-.iPhone.17.-.2026-06-09.at.00.36.12.mov

iOS: mWeb Safari

Simulator.Screen.Recording.-.iPhone.17.-.2026-06-09.at.00.38.40.mov

MacOS: Chrome / Safari

mac-desktop-1.mov

mac-desktop-2.mov

mountiny

@Expensify/design Please give it a look

shawnborton · 2026-06-08T14:52:52Z

Works well on my end 👍

OSBotify · 2026-06-08T15:36:36Z

✋ 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 · 2026-06-08T15:38:26Z

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

github-actions · 2026-06-08T15:43:48Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #92525.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-9ee91f7c604-9a6f6b8-3602e308c4b4ac4f56a006977d97af9a194febd2/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-9ee91f7-9a6f6b8-7b120f771be3e6088abf98d744c258919f0195b3/index.html

Web 🕸️
https://92525.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-06-09T04:34:54Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.4.1-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-06-09T04:36:21Z

Help site review — no docs changes required

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

Conclusion: No help site updates are needed.

Why:

This PR is a purely visual, web-only hover interaction: hovering over a map distance expense receipt thumbnail overlays the full distance e-receipt (map + amount + waypoints), scaled with object-fit: contain to fit the existing receipt box without resizing it. It's a presentation refinement to match Expensify Classic.
It introduces no new feature, setting, tab, label, button, or change to any user-facing workflow. The only changes are a new internal component (HoveredDistanceEReceipt), gating logic in MoneyRequestReceiptView, and a CSS style.
The relevant article — Distance Expenses — documents how to create and edit distance expenses and what receipts represent. Help articles intentionally describe workflows and features, not transient UI affordances like hover-to-zoom, so there is nothing to add or correct.

Because no documentation changes are required, I did not create a draft help site PR.

@WojtekBoman, if you believe this hover behavior should be documented (or if I'm missing a customer-facing change), let me know and I'll draft the help site PR.

jponikarchuk · 2026-06-09T05:59:39Z

Deploy Blocker #93001 was identified to be related to this PR.

jponikarchuk · 2026-06-09T06:16:02Z

Deploy Blocker #93004 was identified to be related to this PR.

mitarachim · 2026-06-09T07:19:31Z

Deploy Blocker #93010 was identified to be related to this PR.

mountiny · 2026-06-09T09:29:59Z

Ended up reverting so we can handle those edge cases in v2

OSBotify · 2026-06-10T00:37:32Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.4.1-6 🚀

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

melvin-bot Bot assigned WojtekBoman Jun 3, 2026

feat: show full distance e-receipt on hover for map distance requests

863ed13

WojtekBoman force-pushed the feat/zoom-map-e-receipts branch from fb5d8c4 to 863ed13 Compare June 3, 2026 14:36

WojtekBoman mentioned this pull request Jun 3, 2026

Allow receipt zooming where customers can roll over receipts with the mouse to zoom in #90793

Open

This comment has been minimized.

Sign in to view

WojtekBoman marked this pull request as ready for review June 3, 2026 15:17

WojtekBoman requested review from a team as code owners June 3, 2026 15:17

melvin-bot Bot requested review from QichenZhu and heyjennahay and removed request for a team June 3, 2026 15:17

chatgpt-codex-connector Bot reviewed Jun 3, 2026

View reviewed changes

Comment thread src/components/ReportActionItem/MoneyRequestReceiptView.tsx Outdated

mountiny requested review from Copilot and mountiny June 3, 2026 15:43

Copilot started reviewing on behalf of mountiny June 3, 2026 15:43 View session

Copilot AI reviewed Jun 3, 2026

View reviewed changes

trjExpensify requested review from trjExpensify and removed request for heyjennahay June 3, 2026 21:46

trjExpensify previously approved these changes Jun 3, 2026

View reviewed changes

QichenZhu reviewed Jun 4, 2026

View reviewed changes

QichenZhu suggested changes Jun 4, 2026

View reviewed changes

Comment thread src/components/ReportActionItem/HoveredDistanceEReceipt.tsx Outdated

Comment thread src/components/ReportActionItem/MoneyRequestReceiptView.tsx Outdated

fix: show distance e-receipt on hover for merged expenses, fix receip…

cb495f6

…t clicks

WojtekBoman dismissed trjExpensify’s stale review via cb495f6 June 8, 2026 09:17

This comment has been minimized.

Sign in to view

QichenZhu approved these changes Jun 8, 2026

View reviewed changes

mountiny previously approved these changes Jun 8, 2026

View reviewed changes

Comment thread src/components/ReportActionItem/HoveredDistanceEReceipt.tsx Outdated

Comment thread src/components/ReportActionItem/MoneyRequestReceiptView.tsx

tidy distance e-receipt hover per review

18e68b0

WojtekBoman dismissed mountiny’s stale review via 18e68b0 June 8, 2026 14:29

mountiny approved these changes Jun 8, 2026

View reviewed changes

mountiny merged commit 9ee91f7 into Expensify:main Jun 8, 2026
33 checks passed

OSBotify mentioned this pull request Jun 9, 2026

Deploy Checklist: New Expensify 2026-06-09 #92988

Closed

applause-bot Bot mentioned this pull request Jun 9, 2026

[Due for payment 2026-06-17] [Due for payment 2026-06-17] Distance - Full receipt appears when hovered over odometer receipt #93001

Closed

7 tasks

applause-bot Bot mentioned this pull request Jun 9, 2026

[Due for payment 2026-06-17] [Due for payment 2026-06-17] Distance - Only the map appears when hovered after closing RHP #93004

Closed

7 tasks

applause-bot Bot mentioned this pull request Jun 9, 2026

[Due for payment 2026-06-17] [Due for payment 2026-06-17] Distance - Previous map receipt appears on hover after editing distance offline #93010

Closed

7 tasks

mountiny mentioned this pull request Jun 9, 2026

[CP Staging] Revert "feat: show full distance e-receipt on hover for map distance requests" #93021

Merged

		const isDistanceRequest = isDistanceRequestTransactionUtils(transaction);
		const isMapDistanceRequest = !!transaction && isDistanceRequest && !isManualDistanceRequest(transaction);

		@@ -623,23 +623,28 @@ function MoneyRequestReceiptView({
		isEnabled={canZoomReceipt}

Conversation

WojtekBoman commented Jun 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

codecov Bot commented Jun 3, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

github-actions Bot commented Jun 3, 2026

Uh oh!

This comment has been minimized.

shawnborton commented Jun 3, 2026

Uh oh!

shawnborton commented Jun 3, 2026

Uh oh!

melvin-bot Bot commented Jun 3, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

QichenZhu Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Steps to reproduce:

Expected result:

Actual result:

Uh oh!

WojtekBoman Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

WojtekBoman Jun 8, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

trjExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

QichenZhu left a comment

Choose a reason for hiding this comment

Uh oh!

dannymcclain commented Jun 4, 2026

Uh oh!

Uh oh!

Uh oh!

WojtekBoman commented Jun 8, 2026

Uh oh!

github-actions Bot commented Jun 8, 2026

Uh oh!

This comment has been minimized.

QichenZhu commented Jun 8, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

shawnborton commented Jun 8, 2026

Uh oh!

Uh oh!

OSBotify commented Jun 8, 2026

Uh oh!

github-actions Bot commented Jun 8, 2026

Uh oh!

github-actions Bot commented Jun 8, 2026

WojtekBoman commented Jun 3, 2026 •

edited

Loading

codecov Bot commented Jun 3, 2026 •

edited by github-actions Bot

Loading

QichenZhu Jun 4, 2026 •

edited

Loading