Skip to content

fix: resolve deploy blockers and add hover/tooltip to receipt action buttons#84497

Merged
puneetlath merged 23 commits intoExpensify:mainfrom
TaduJR:feat-Allow-Multiple-Receipts-to-Be-Attached-to-a-Single-Expense
Mar 18, 2026
Merged

fix: resolve deploy blockers and add hover/tooltip to receipt action buttons#84497
puneetlath merged 23 commits intoExpensify:mainfrom
TaduJR:feat-Allow-Multiple-Receipts-to-Be-Attached-to-a-Single-Expense

Conversation

@TaduJR
Copy link
Contributor

@TaduJR TaduJR commented Mar 7, 2026

Explanation of Change

Fixes 5 deploy blockers and 1 additional deploy blocker found during QA of the receipt action buttons (Add Receipt + Enlarge) introduced in the original PR #83994:

  1. Buttons don't appear after hovering during image load ([Due for payment 2026-03-30] Web - Expense - Buttons do not appear when hovering over receipt while it is loading #84354) — Added isMouseInsideRef to track mouse position independently of hover state. When isLoading transitions to false, a useEffect re-triggers
    onMouseEnter if the mouse is still inside the receipt area, so buttons appear without requiring the user to move the mouse out and back in.

  2. Blue focus ring on enlarge button after pressing ESC ([Due for payment 2026-03-30] Web - Expense - Full screen button has blue border after closing receipt view with ESC key #84355) — Replaced PressableWithoutFeedback with PressableWithoutFocus on the enlarge button and added styles.noOutline. PressableWithoutFocus calls
    blur() on press, preventing the browser's default focus ring from persisting after the receipt modal is closed with ESC.

  3. No error modal for oversized/invalid attachments ([Due for payment 2026-03-30] Expense - No error modal when sending large attachment from receipt button #84356) — Integrated useFilesValidation hook (same pattern used by ReportActionCompose) to validate file size, type, and PDF password protection before
    uploading. Added acceptedFileTypes restriction to AttachmentPicker so the OS file dialog pre-filters to valid receipt extensions. Renders AttachmentErrorModal and PDFValidationComponent for user feedback.

  4. Report doesn't scroll down after adding attachment ([Due for payment 2026-03-30] Expense - Report does not scroll down after sending attachment #84359) — Changed notifyReportID from moneyRequestReport?.reportID ?? report.reportID to report.reportID. The attachment is posted to the transaction thread
    (report), so that's the report that needs the scroll-to-bottom notification — not the parent IOU report.

  5. Buttons persist without hover on touchscreen laptops ([Due for payment 2026-03-30] Chat Report View - Enlarge and plus buttons on receipt image persist without hover #84388) — Replaced canUseTouchScreen() with hasHoverSupport() in both useHover.ts and MoneyRequestReceiptView.tsx. canUseTouchScreen() checks
    navigator.maxTouchPoints > 0 which returns true on touchscreen laptops (e.g., Lenovo Flex 5i) even though they have a mouse — blocking hover state updates entirely. hasHoverSupport() uses CSS media query (hover: hover) and (pointer: fine) which correctly identifies hover capability regardless of touch presence.

  6. Button icons hard to see when PDF receipt added offline ([Due for payment 2026-03-30] Android - Expense - Button icons are hard to see when PDF receipt is added offline #84367) — Used shouldDisableOpacity on OfflineWithFeedback to prevent blanket opacity: 0.5 from fading the action buttons when offline. Applied offlineFeedbackPending style manually to just the receipt image wrapper, so the image correctly fades while buttons remain at full opacity and usable.

Fixed Issues

$ #84354
$ #84355
$ #84356
$ #84359
$ #84388
$ #84367
PROPOSAL:

Tests

Prerequisite: Create an expense with a receipt in a workspace chat and open the expense.

#84354 — Buttons appear after hovering during image load:

  1. Open the expense
  2. Quickly hover over the receipt while it is still loading
  3. Keep the mouse over the receipt until loading completes
  4. Verify the enlarge and add buttons appear on the receipt without needing to move the mouse away and back

#84355 — No blue focus ring on enlarge button after ESC:

  1. Hover over the receipt
  2. Click the full screen (enlarge) button
  3. Close the receipt view with the ESC key
  4. Hover over the receipt again
  5. Verify the enlarge button does not have a blue focus border

#84356 — Error modal for oversized/invalid attachments:

  1. Hover over the receipt
  2. Click the Add (+) button
  3. Select an attachment larger than 25 MB
  4. Verify an error modal appears stating the file is too large
  5. Repeat with an invalid file type and verify the file picker filters it out

#84359 — Report scrolls down after adding attachment:

  1. Create two expenses (one must have a receipt) so the report uses the table view
  2. Open the expense with receipt
  3. Send enough messages so the report is scrollable
  4. Scroll to the top
  5. Hover over the receipt and click the Add (+) button
  6. Add a valid attachment
  7. Verify the report scrolls down to show the newly sent attachment

#84388 — Buttons show/hide on hover (touchscreen laptop):

  1. On a device with both touchscreen and mouse (e.g., Lenovo Flex 5i)
  2. Open an expense with a receipt
  3. Verify the buttons are hidden by default
  4. Hover over the receipt with the mouse
  5. Verify the buttons appear
  6. Move the mouse away from the receipt
  7. Verify the buttons disappear

#84367 — Button icons visible when PDF receipt added offline:

  1. Enable dark mode
  2. Go to workspace chat
  3. Create an expense without a receipt
  4. Open the expense
  5. Go offline
  6. Tap the receipt area and add a PDF receipt
  7. Verify the add and enlarge button icons on the receipt are clearly visible and not faded out
  8. Go back online
  9. Verify the buttons remain clearly visible

Tooltip and hover on receipt action buttons:
1. Open an expense with a receipt
2. Hover over the receipt image
3. Verify the add and enlarge buttons appear
4. Hover over the add (+) button
5. Verify a tooltip "Add additional receipt" appears and the button has a hover background
6. Hover over the enlarge button
7. Verify a tooltip "Expand" appears and the button has a hover background
8. Move the mouse away from the receipt
9. Verify the tooltips disappear and buttons hide

  • Verify that no errors appear in the JS console

Offline tests

Same as tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."
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-Native.mp4
Android: mWeb Chrome
iOS: Native
iOS-Native.mp4
iOS: mWeb Safari
iOS-Safari.mp4
MacOS: Chrome / Safari
Mac-Chrome.mp4

@TaduJR TaduJR requested review from a team as code owners March 7, 2026 13:04
@melvin-bot melvin-bot bot requested review from ahmedGaber93 and joekaufmanexpensify and removed request for a team March 7, 2026 13:04
@melvin-bot
Copy link

melvin-bot bot commented Mar 7, 2026

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

@codecov
Copy link

codecov bot commented Mar 7, 2026

Codecov Report

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

Files with missing lines Coverage Δ
src/libs/actions/Report/index.ts 67.40% <100.00%> (+0.29%) ⬆️
src/styles/index.ts 47.42% <ø> (ø)
...ReportActionItem/receiptHoverUtils/index.native.ts 66.66% <66.66%> (ø)
src/hooks/useHover.ts 66.66% <33.33%> (ø)
...nents/ReportActionItem/MoneyRequestReceiptView.tsx 68.21% <68.42%> (+1.27%) ⬆️
...onents/ReportActionItem/receiptHoverUtils/index.ts 0.00% <0.00%> (ø)
... and 11 files with indirect coverage changes

…Multiple-Receipts-to-Be-Attached-to-a-Single-Expense
Copy link
Contributor

@joekaufmanexpensify joekaufmanexpensify left a comment

Choose a reason for hiding this comment

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

Fixing DBs

@ahmedGaber93
Copy link
Contributor

ahmedGaber93 commented Mar 9, 2026

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 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
20260316214029107.mp4
20260316213920573.mp4
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
20260316203940082.mp4
20260316204408887.mp4
20260316204449780.mp4

@ahmedGaber93
Copy link
Contributor

Issue: Buttons don't appear after hovering during image load

Review - Edge case: when uploading the receipt for the first time, the button still disappears.

20260310222420835.mp4

Issue: Blue focus ring on enlarge button after pressing ESC

Review - Regression: enlarge button doesn't have border style when using tab to focus it

Screenshot 2026-03-10 at 10 35 09 PM

It would be good to make the border style clearer for both buttons. Maybe we could use a square border.

Screenshot 2026-03-10 at 10 34 51 PM

Issue: Report doesn't scroll down after adding attachment

Review - Not fixed with me.

20260311001943288.mp4

@melvin-bot
Copy link

melvin-bot bot commented Mar 16, 2026

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

…Multiple-Receipts-to-Be-Attached-to-a-Single-Expense

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
@melvin-bot melvin-bot bot requested a review from puneetlath March 17, 2026 23:53
@puneetlath puneetlath merged commit 215b2f5 into Expensify:main Mar 18, 2026
35 checks passed
@OSBotify
Copy link
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
Contributor

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

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/puneetlath in version: 9.3.41-0 🚀

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

Bundle Size Analysis (Sentry):

@IuliiaHerets
Copy link

Hi @TaduJR. QA team failed this PR with this original issue

1773956892982.Recording__1872.mp4

@TaduJR
Copy link
Contributor Author

TaduJR commented Mar 20, 2026

Hi @TaduJR. QA team failed this PR with this #84356

Hi @IuliiaHerets

Hmm not able to repo on my side. Could you please create an issue for it with the attachment you used to repo if possible?

Thanks!

@TaduJR
Copy link
Contributor Author

TaduJR commented Mar 20, 2026

@IuliiaHerets

Don't forget to tag me there.

@nlemma
Copy link

nlemma commented Mar 20, 2026

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

@IuliiaHerets
Copy link

@TaduJR, issue was logged here

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/cristipaval in version: 9.3.41-4 🚀

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

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants