Skip to content

[Due for payment 2026-10-07] Expense - Floating RHP closes after clicking on the top area within the RHP #102622

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.97-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #101093
Email or phone of affected tester (no customers): jsdoijnodsdisojo@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense.
  4. Open the report.
  5. Click on the area above Submit button within the floating RHP.

Expected Result:

Floating RHP will not close after clicking on the top area within the RHP.

Actual Result:

Floating RHP closes after clicking on the top area within the RHP.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

To be added by Applause Leads

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7273157

Issue OwnerCurrent Issue Owner: @huult

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Sep 30, 2026
  2. applause-bot commented on Sep 30, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/c7ef74440b4f643934cca1fa9e89648a84fd50943bfb4690baca98ff21c18837

  3. melvin-bot commented on Sep 30, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #101093

  4. melvin-bot commented on Sep 30, 2026

    @melvin-bot

    @mountiny @huult you have been assigned to this deploy blocker because you reviewed the offending PR: #101093

  5. melvin-bot commented on Sep 30, 2026

    @melvin-bot

    @BartekObudzinski you have been assigned to this deploy blocker because you authored the offending PR: #101093

  6. melvin-bot commented on Sep 30, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  7. github-actions commented on Sep 30, 2026

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  8. MelvinBot commented on Sep 30, 2026

    @MelvinBot
    Contributor

    Deploy Blocker Analysis

    Causing PR: feat: use floating RHP style on web (Expensify/App#101093). Confidence: high (confirmed from code, not reproduced in a browser).

    Root cause: The PR adds three transparent overlay bands around the floating card. The top band is only 12px tall, but it reuses BaseOverlay, which has a fixed 30px click target inside it. Nothing clips that target, so a close-on-click strip covers about 18px of the card's top edge. Clicking there calls navigation.goBack() and closes the RHP.

    Recommended fix (roll forward): Add styles.overflowHidden to the root Animated.View style in BaseOverlay.tsx:63-67. This clips the click target to the 12px band. If a fix can't land quickly, reverting the PR is a clean fallback.

    Investigation details
    1. The bands render after the card, so they sit on top of it: RightModalNavigator.tsx:575-599. They only show when shouldUseCenteredFrame is true (a wide report or expense in the RHP), which is why the report flow triggers it.
    2. The top band has top: 0 and positionBottomValue = windowHeight - 12 (L213, L580), so it is 12px tall.
    3. BaseOverlay's first child is a PressableWithoutFeedback with styles.draggableTopBar (height: 30): BaseOverlay.tsx:74-81, styles/index.ts:5496-5499.
    4. The card starts at top: 12 (styles/index.ts:89), so y = 12–30px across the card is a hidden click target.
    5. The click runs handleFloatingCardGapPress → handleOverlayPress → navigation.goBack() (L240-L262).

    The bottom band overflows too, but below the viewport, so it's harmless. None of the other 45 PRs in Deploy Checklist: New Expensify 2026-09-30 touch RHP navigation, overlays, or card styles.

    An alternative fix is to give RHPOverlay an option that renders one full-size click target without the 30px drag bar, and use it for the three gap bands.


    Next Steps: Reply with @MelvinBot implement this to create a draft PR, or @MelvinBot <your feedback> to refine this analysis.


    view run

  9. BartekObudzinski commented on Sep 30, 2026

    @BartekObudzinski
    Contributor

    I will check it

  10. BartekObudzinski commented on Sep 30, 2026

    @BartekObudzinski
    Contributor

    pr ready to review #102638

  11. IuliiaHerets commented on Sep 30, 2026

    @IuliiaHerets

    Chrome / v9.4.99-0
    Passed

    bandicam.2026-09-30.21-01-56-254.mp4
  12. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Sep 30, 2026
  13. changed the title [-]Expense - Floating RHP closes after clicking on the top area within the RHP[/-] [+][Due for payment 2026-10-07] Expense - Floating RHP closes after clicking on the top area within the RHP[/+] on Sep 30, 2026
  14. melvin-bot commented on Sep 30, 2026

    @melvin-bot

    @huult

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.99-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-10-07. 🎊

    The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions