Skip to content

feat: Allow admins to mark report with non-reimbursable expenses as paid and show decision modal if user try to pay via ACH#83329

Merged
cristipaval merged 31 commits intoExpensify:mainfrom
samranahm:81721/non-reimbursableexpenses-mark-as-paid
Apr 1, 2026
Merged

feat: Allow admins to mark report with non-reimbursable expenses as paid and show decision modal if user try to pay via ACH#83329
cristipaval merged 31 commits intoExpensify:mainfrom
samranahm:81721/non-reimbursableexpenses-mark-as-paid

Conversation

@samranahm
Copy link
Copy Markdown
Contributor

@samranahm samranahm commented Feb 24, 2026

Explanation of Change

Fixed Issues

$ #81721
PROPOSAL: #81721 (comment)

Tests

Precondition:

  • Workspace is connected to Business bank account
  • Admin Invited a member to workspace

Test:

  1. As a member, submit a non-reimbursable expense in the workspace chat.
  2. As an admin, open the expense report submitted by the member and approve it.
  3. Verify that the Pay button appears on the report preview with a dropdown menu.
  4. Select “Business bank account” and verify that an error modal appears with the message: "Cannot pay with direct payment".
  5. Press “Got it”.
  6. Choose “Mark as paid” and verify that the report is successfully marked as paid.
  7. Open the expense report > More > “Cancel payment”.
  8. Verify that the Pay button appears again in the money request report header.
  9. Repeat steps 4–6 and verify that the Pay button behaves the same.
  10. Cancel the payment again and open Report page > To-do > Pay.
  11. Verify that the non-reimbursable expense is listed here and it has a Pay button with a dropdown menu.
  12. Verify that the Pay button includes both options ACH and Mark as paid.
  13. Repeat steps 4–6 and verify that the Pay button behaves the same.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as test
// TODO: These must be filled out, or the issue title must include "[No QA]."

  • 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 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
Android.mWeb.Chrome.mp4
iOS: Native
IOS.Native.mp4
iOS: mWeb Safari
IOS.mWeb.Safari.mp4
MacOS: Chrome / Safari
macOS.Chrome.mp4

Copilot AI review requested due to automatic review settings February 24, 2026 14:37
@samranahm samranahm requested review from a team as code owners February 24, 2026 14:37
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Feb 24, 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

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Enables admins to mark expense reports that contain only non‑reimbursable expenses as paid (via “Pay elsewhere”), and shows a blocking decision modal when attempting to pay such reports via direct payment methods (e.g., ACH).

Changes:

  • Show Pay actions/buttons for reports with only non‑reimbursable transactions across report header/preview and search flows.
  • Block non‑reimbursable reports from being paid via direct payment methods by showing a localized DecisionModal.
  • Add new i18n strings for the non‑reimbursable payment error messaging.

Reviewed changes

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

Show a summary per file
File Description
src/pages/Search/SearchPage.tsx Adjusts bulk-pay “only show pay elsewhere” logic to exclude only-non-reimbursable reports.
src/libs/actions/IOU/index.ts Extends canIOUBePaid() to treat only-non-reimbursable reports as eligible when showing “pay elsewhere”.
src/libs/SearchUIUtils.ts Adds PAY action for only-non-reimbursable reports and updates pay-elsewhere gating.
src/libs/ReportPrimaryActionUtils.ts Allows primary Pay action for only-non-reimbursable expense reports.
src/libs/ReportPreviewActionUtils.ts Allows preview Pay action for only-non-reimbursable expense reports.
src/libs/MoneyRequestReportUtils.ts Adjusts preview button amount display for only-non-reimbursable reports.
src/components/SelectionListWithSections/Search/ActionCell/PayActionCell.tsx Adds DecisionModal when attempting to pay non-reimbursable reports via direct payment methods.
src/components/ReportActionItem/MoneyRequestReportPreview/MoneyRequestReportPreviewContent.tsx Shows Pay button for only-non-reimbursable reports and displays DecisionModal on direct-payment attempts.
src/components/ProcessMoneyReportHoldMenu.tsx Adds callback to surface the non-reimbursable direct-payment error from the hold menu flow.
src/components/MoneyReportHeader.tsx Shows Pay button for only-non-reimbursable reports and displays DecisionModal on direct-payment attempts.
src/languages/*.ts Adds localized strings for the new non-reimbursable payment error modal.

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

Copy link
Copy Markdown

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

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: 6d92ab3e55

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

@codecov
Copy link
Copy Markdown

codecov bot commented Feb 24, 2026

Codecov Report

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

Files with missing lines Coverage Δ
...ReportPreview/MoneyRequestReportPreviewContent.tsx 61.44% <100.00%> (+0.15%) ⬆️
...RequestReportPreview/ReportPreviewActionButton.tsx 100.00% <ø> (ø)
src/libs/MoneyRequestReportUtils.ts 77.94% <100.00%> (+1.01%) ⬆️
src/libs/ReportPreviewActionUtils.ts 92.66% <100.00%> (ø)
src/libs/ReportPrimaryActionUtils.ts 91.78% <100.00%> (ø)
src/libs/ReportSecondaryActionUtils.ts 92.91% <100.00%> (ø)
src/libs/ReportUtils.ts 79.60% <100.00%> (ø)
src/libs/SearchUIUtils.ts 68.37% <100.00%> (+0.03%) ⬆️
src/libs/actions/IOU/index.ts 74.57% <100.00%> (+<0.01%) ⬆️
src/libs/actions/OnyxDerived/configs/todos.ts 100.00% <100.00%> (ø)
... and 7 more
... and 8 files with indirect coverage changes

@samranahm
Copy link
Copy Markdown
Contributor Author

@trjExpensify @jamesdeanexpensify Can you confirm the copy please

title: "Cannot pay via direct payment"
prompt: "This report does't have reimbursable expenses and cannot be paid via direct payment. Use "Pay elsewhere" to mark it as paid instead.'"

NewDot.mp4

OldDot

Screenshot 2026-02-24 at 9 11 07 PM

@jamesdeanexpensify
Copy link
Copy Markdown
Contributor

Cannot pay report
This report has no reimbursable expenses. Please mark it as paid instead.

Copy link
Copy Markdown
Contributor

@trjExpensify trjExpensify left a comment

Choose a reason for hiding this comment

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

This is one of @joekaufmanexpensify's 👍

For this copy:

Image

@jamesdeanexpensify I suggested a copy update here to tighten this up a bit. What do you think about the below:

Cannot pay via Expensify
The report doesn’t have reimbursable expenses. Double check the expenses, or manually mark as paid.

[Got it]

@jamesdeanexpensify
Copy link
Copy Markdown
Contributor

That also works!

@trjExpensify
Copy link
Copy Markdown
Contributor

Oh haha, I totally went straight to the review mode and didn't see that from earlier. I think what I like about the version I suggested is that the payment method is a bit clearer and linked. You can pay the report, just not via Expensify.

@jamesdeanexpensify
Copy link
Copy Markdown
Contributor

Makes sense. What do you mean by the payment method is linked?

@trjExpensify
Copy link
Copy Markdown
Contributor

The difference between:

Cannot pay via Expensify

AND

Cannot pay report

The first option is an indicator of the payment method (in-app via Expensify), the latter could be misconstrued as not being able to pay the report at all.

@MelvinBot
Copy link
Copy Markdown
Contributor

🤖 Code Review (Updated)

Good progress since the last review. The main feedback items have been addressed:

Resolved since last review:

  • ProcessMoneyReportHoldMenu now accepts a transactions prop and both parent components (MoneyReportHeader, MoneyRequestReportPreviewContent) pass their hook-loaded transactions through. This fixes the inconsistent data source issue I flagged earlier.
  • The !isApprove guard was already added to prevent the non-reimbursable check from blocking approval flows in the hold menu.

Remaining items (low severity, non-blocking):

  1. useSearchBulkActions bulk pay still aborts entirely — When the non-reimbursable check fires during bulk pay (line ~563), the entire operation aborts for all selected reports. This is consistent with the other early-return patterns (offline, delegate access) in the same callback, so it appears intentional. Just confirming this is the desired behavior since the error message says "One or more selected reports" suggesting partial processing might be possible.

  2. shouldBlockDirectPayment and showNonReimbursablePaymentErrorModal are recreated on every render — In useNonReimbursablePaymentModal.tsx, both functions are plain arrow functions without useCallback. Since they're passed as props through multiple component layers (e.g., MoneyReportHeaderProcessMoneyReportHoldMenu), they trigger unnecessary re-renders. This is minor and unlikely to cause user-visible issues, but wrapping them in useCallback would be consistent with the rest of the codebase's memoization patterns.

Overall this PR looks ready. The core logic is sound, tests cover the new paths, copy has been approved, and the earlier review feedback has been incorporated.

Copy link
Copy Markdown

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

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: ed5bbfdf9b

ℹ️ 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 didExportFail = !isExported && hasExportError;

if (isExpense && isReportPayer && isPaymentsEnabled && isReportFinished && reimbursableSpend !== 0) {
if (isExpense && isReportPayer && isPaymentsEnabled && isReportFinished && (reimbursableSpend !== 0 || hasOnlyNonReimbursableTransactions(report?.reportID))) {
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 Use caller transactions when deriving preview PAY action

canPay() now depends on hasOnlyNonReimbursableTransactions(report?.reportID) but does not use the transactions that getReportPreviewAction() already receives, so it falls back to global Onyx state. If preview transactions are available before the collection is hydrated (or differ from global cache), this returns false and the PAY action is omitted for non-reimbursable-only reports. Threading the provided transactions through this check avoids stale/global-state misclassification.

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.

I think we should address this @samranahm @situchan. We added support for passing the transactions to hasOnlyNonReimbursableTransactions. Why don't we use it and rely on the deprecatedReportsTransactions?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated the logic to pass transactions instead of relying on deprecatedReportsTransactions.

@samranahm
Copy link
Copy Markdown
Contributor Author

@cristipaval friendly bump.

@trjExpensify
Copy link
Copy Markdown
Contributor

Maybe not bug but it's confusing to show the same amount for both "only" and "total"

Screenshot 2026-03-28 at 1 42 25 AM

This isn't great though. @samranahm @situchan can you outline the case for it in numbered steps? CC: @joekaufmanexpensify

@samranahm
Copy link
Copy Markdown
Contributor Author

samranahm commented Mar 30, 2026

@trjExpensify here are the steps to reproduce #83329 (comment)

  1. Disable approvals
  2. Submit two expenses in the workspace, one reimbursable and one non-reimbursable
  3. Place the non-reimbursable expense on hold
  4. Admin then clicks the “Pay” button

We have consistent behaviour with staging.

}

// For reports with only non-reimbursable expenses, show total display spend for Mark as paid.
if (hasOnlyNonReimbursableTransactions(report?.reportID)) {
Copy link
Copy Markdown
Contributor

@cristipaval cristipaval Mar 31, 2026

Choose a reason for hiding this comment

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

Same as here, why do we rely on the global-deprecated-cached transactions? Can't we pass them as parameters?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

We absolutely can, updated the logic.

const {reimbursableSpend} = getMoneyRequestSpendBreakdown(report);

if (isReportPayer && isExpenseReport && arePaymentsEnabled && isReportFinished && reimbursableSpend !== 0) {
if (isReportPayer && isExpenseReport && arePaymentsEnabled && isReportFinished && (reimbursableSpend !== 0 || hasOnlyNonReimbursableTransactions(report?.reportID))) {
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.

again, we shouldn't rely on the global cached transactions since they are deprecated

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Updated

Copy link
Copy Markdown
Contributor

@cristipaval cristipaval left a comment

Choose a reason for hiding this comment

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

Added some comments

@joekaufmanexpensify
Copy link
Copy Markdown
Contributor

@trjExpensify here are the steps to reproduce #83329 (comment)

  1. Disable approvals
  2. Submit two expenses in the workspace, one reimbursable and one non-reimbursable
  3. Place the non-reimbursable expense on hold
  4. Admin then clicks the “Pay” button

We have consistent behaviour with staging.

Interesting. I agree that behavior seems incorrect. I'm not convinced the admin needs to confirm anything in that case. I wonder if we could just pay the unheld expenses and split the held non-reimbursable expenses to a new report. Alternatively, we could warn them what would happen if the admin proceeds, so they're aware. But IDT we should offer two pay buttons to pay the same amount...

If this is on staging, we prob don't need to handle it here though, yeah? Since this PR primarily deals with non-reimbursable reports.

@trjExpensify
Copy link
Copy Markdown
Contributor

Yeah, as it's on staging, I agree with it being out of scope of this PR.

But IDT we should offer two pay buttons to pay the same amount...

Same here. Thinking about it though, I think the improvement comes sooner probably.

  1. Be on a workspace with manual submission + approvals disabled + payments enabled.
  2. Create a reimbursable expense
  3. Create a non-reimbursable expense
  4. Hold the non-reimbursable expense
  5. Submit the report
  6. Pay the report
  7. Get the double button modal

^^ at step 5, we should consider keeping held expenses back. I just tried to unhold an expense on a closed report and it outright fails:

image
Throw ExpException - 1d43fd1c51c1c5e261ca4ece42eae341 ~~ message: '403 Transaction not accessible' source: 'auth-via-api' exceptionMessage: 'Auth UnHoldRequest returned an error' exceptionFile: '/git/releases/expensify.com/be20996/lib/Auth.php' exceptionLine: '143' exceptionCode: '403'

Hitting this code block in the UnHoldRequest command.

 // Verify that we can modify the transaction to set the hold state
    if (auth.report.verifyWrite(db, reportID, accountID, Report::STATE_APPROVED)) {
        STHROW("403 Transaction not accessible");
    }

@joekaufmanexpensify
Copy link
Copy Markdown
Contributor

Ah, yeah that makes sense to me.

@github-actions
Copy link
Copy Markdown
Contributor

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

@github-actions

This comment has been minimized.

1 similar comment
@github-actions
Copy link
Copy Markdown
Contributor

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

Android 🤖 iOS 🍎
⏩ SKIPPED ⏩ ❌ FAILED ❌
The build for Android was skipped The QR code can't be generated, because the iOS build failed
Web 🕸️
⏩ SKIPPED ⏩
The build for Web was skipped

👀 View the workflow run that generated this build 👀

@cristipaval
Copy link
Copy Markdown
Contributor

Thanks @samranahm!

@situchan, could you quickly retest on a platform to confirm it still works as expected? 🙏

@situchan
Copy link
Copy Markdown
Contributor

situchan commented Apr 1, 2026

retested. works as expected

Screen.Recording.2026-04-01.at.4.25.53.PM.mov

Copy link
Copy Markdown
Contributor

@cristipaval cristipaval left a comment

Choose a reason for hiding this comment

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

Thank you all for working on this!

@cristipaval cristipaval merged commit 1617cbc into Expensify:main Apr 1, 2026
33 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 1, 2026

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

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 1, 2026

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

@OSBotify
Copy link
Copy Markdown
Contributor

OSBotify commented Apr 2, 2026

🚀 Deployed to staging by https://github.com/cristipaval in version: 9.3.52-0 🚀

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

Bundle Size Analysis (Sentry):

@MelvinBot
Copy link
Copy Markdown
Contributor

🤖 I reviewed the changes in this PR and confirmed that help site updates are needed. I've created a draft PR with the required changes:

Draft PR: #86995

Changes made:

  1. Understanding-Report-Statuses-and-Actions.md — Removed the incorrect statement that "Approved" is the final status for reports containing only non-reimbursable expenses. With this PR, admins can now mark those reports as paid, so they can reach "Paid" status.

  2. Pay-Expenses.md — Added a new FAQ entry explaining that reports with only non-reimbursable expenses cannot be paid via ACH, and that admins should use Mark as paid instead.

I created this PR from an upstream branch since I don't have push access to your fork.

To take ownership of this branch and be able to push updates, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream claude-helpDocsNonReimbursablePay
git checkout -b claude-helpDocsNonReimbursablePay upstream/claude-helpDocsNonReimbursablePay
git push -u origin claude-helpDocsNonReimbursablePay

Then you can close the draft PR and open a new one from your fork.

Please mark it as "Ready for review" when it is ready for review.

@mitarachim
Copy link
Copy Markdown

@samranahm This PR is failing because of a regression issue #87018

The issue is reproducible in: Web, Android

Bug7120186_1775162143393.bandicam_2026-04-02_23-34-18-889.mp4

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.