Skip to content

[Due for payment 2026-05-29] [$250] DEV : Unable to scroll in "More" bottom sheet of expenses #86593

Closed

Description

@m-natarajan

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number:
Reproducible in staging?: Needs Reproduction (Unable to reproduce)
Reproducible in production?: Needs Reproduction
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @ShridharGoel
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

  1. Go to reports tab.
  2. Open any expense which is in draft state.
  3. Click on "More".
  4. Try scrolling in the more section (if the number of options are enough to scroll, else try with another expense)

Expected Result:

User able to scroll "More" menu options

Actual Result:

Unable to scroll in "More" bottom sheet

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

Screen.Recording.2026-03-28.at.2.46.40.AM.mov

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mallenexpensify
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022037692302907449843
  • Upwork Job ID: 2037692302907449843
  • Last Price Increase: 2026-03-28
  • Automatic offers:
    • FitseTLT | Reviewer | 111398220

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Mar 28, 2026
  2. MelvinBot commented on Mar 28, 2026

    @MelvinBot
    Contributor

    Proposal

    What is the root cause of that problem?

    The PopoverMenu component defaults shouldUseScrollView to false (PopoverMenu.tsx:297). When the "More" button is tapped on an expense, MoneyRequestHeaderSecondaryActions renders a ButtonWithDropdownMenu without passing shouldPopoverUseScrollView={true} (MoneyRequestHeaderSecondaryActions.tsx:501-510). This means the menu items are wrapped in a plain <View> instead of a <ScrollView> (PopoverMenu.tsx:187-193).

    On iOS mWeb Safari (small screen), the popover renders as a BOTTOM_DOCKED modal with overflow: 'hidden' on its container (ModalStyleUtils.ts:234), and the inner content has a maxHeight of 432px (POPOVER_MENU_MAX_HEIGHT_MOBILE). For draft/open expense reports, up to 7-8 secondary actions can appear (Hold, Split, Merge, Duplicate, Move Expense, View Details, Delete, and potentially Reject), totaling ~480px+ of content height. Since the items are in a plain View (not a ScrollView), the overflowing items are simply clipped and unreachable — there is no scroll mechanism.

    What changes do you think we should make in order to solve the problem?

    Pass shouldPopoverUseScrollView={true} from MoneyRequestHeaderSecondaryActions to ButtonWithDropdownMenu. This enables PopoverMenu to use a <ScrollView> wrapper instead of a plain <View>, allowing the user to scroll through menu items that exceed the 432px mobile max height.

    What alternative solutions did you explore? (Optional)

    1. Change the default of shouldUseScrollView to true in PopoverMenu — This would fix the issue globally but could have unintended side effects on popover measurement logic in other callers that don't need scrolling.
    2. Auto-detect overflow and conditionally enable ScrollView based on item count — More elegant but adds complexity for a straightforward fix.
    3. Increase POPOVER_MENU_MAX_HEIGHT_MOBILE — This would only delay the problem until more actions are added, and doesn't address the fundamental lack of scrolling.

    Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

  3. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Mar 28, 2026
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Mar 28, 2026
  5. melvin-bot commented on Mar 28, 2026

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @FitseTLT (External)

  6. melvin-bot commented on Mar 28, 2026

    @melvin-bot
  7. changed the title [-]DEV : Unable to scroll in "More" bottom sheet of expenses[/-] [+][$250] DEV : Unable to scroll in "More" bottom sheet of expenses[/+] on Mar 28, 2026
  8. Coincatcher commented on Mar 28, 2026

    @Coincatcher

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    On iOS mWeb Safari, the "More" bottom sheet in expense views does not scroll when the number of options exceeds the visible area.

    What is the root cause of that problem?

    This is a known iOS Safari/WebKit issue with overflow: auto inside bottom sheet modals that use position: fixed or CSS transforms for positioning. Safari on iOS has inconsistent touch event handling when a scrollable element is nested inside a transformed container — the browser captures the touch for the parent drag gesture instead of passing it to the child scroll container.

    In the Expensify App, the BottomSheet component likely uses react-native-reanimated or a similar library with transform: translateY() for the sheet animation. On iOS Safari (mWeb), this creates a scrolling dead zone because WebKit prioritizes the outer pan gesture recognizer over the inner ScrollView.

    What changes do you think we should make in order to fix the problem?

    Fix: Add -webkit-overflow-scrolling: touch and proper touch handling for iOS mWeb

    1. In the bottom sheet content wrapper (likely in src/components/BottomSheet/ or src/components/Popover/), add platform-specific styling for web:

      • Set -webkit-overflow-scrolling: touch on the scrollable content area
      • Add overscroll-behavior: contain to prevent scroll chaining to the parent
      • Ensure touch-action: pan-y is set on the scrollable content
    2. If the bottom sheet uses gesture-based dismissal, add a scroll detection guard that prevents the dismiss gesture when the user is scrolling within the content area (check scrollTop > 0 before allowing downward pan).

    Files to modify:

    • src/components/PopoverMenu/index.tsx or the bottom sheet content wrapper
    • Platform-specific style adjustments for web/mWeb
  9. layacat commented on Mar 28, 2026

    @layacat
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    Unable to scroll in "More" bottom sheet of expenses

    What is the root cause of that problem?

    We forgot to pass the props shouldPopoverUseScrollView here:

    <ButtonWithDropdownMenu
    ref={dropdownMenuRef}
    success={false}
    onPress={() => {}}
    shouldAlwaysShowDropdownMenu
    customText={translate('common.more')}
    options={applicableSecondaryActions}
    isSplitButton={false}
    wrapperStyle={!isNarrow && !hasPrimaryAction ? [styles.flexGrow4] : undefined}
    />

    ===> Our ButtonWithDropdownMenu content menu can't be scrollable because it's not use scrollview. That's the RCA.

    What changes do you think we should make in order to solve the problem?

    Let's only use the shouldPopoverUseScrollView when our applicableSecondaryActions reaches the threadhold like we did in other places.

    <ButtonWithDropdownMenu
    // Add this extra props
    shouldPopoverUseScrollView={applicableSecondaryActions.length >= CONST.DROPDOWN_SCROLL_THRESHOLD}
    
    />
  10. sayanget commented on Mar 28, 2026

    @sayanget

    🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

  11. melvin-bot commented on Mar 28, 2026

    @melvin-bot

    ✅ Contributor details stored successfully. Thank you for contributing to Expensify!

  12. github-actions commented on Mar 28, 2026

    @github-actions
    Contributor

    ⚠️ @sayanget Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

  13. 52 remaining items

  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on May 25, 2026
  15. melvin-bot commented on May 28, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  16. mallenexpensify commented on May 29, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor: @nabi-ebrahimi paid $250 via Upwork
    Contributor+: @FitseTLT paid $250 via Upwork

    @nabi-ebrahimi can you please accept the job below? Please reply here and tag me once you have.
    If you're not sent an offer in Upwork when you're assigned to an issue, and an Upwork job exists, please submit a proposal.
    https://www.upwork.com/jobs/~022060429115978038896

    ^ Test case created. Thx

  17. nabi-ebrahimi commented on May 31, 2026

    @nabi-ebrahimi
    Contributor

    @mallenexpensify, thanks for following up on this. Unfortunately, I’m not able to submit a proposal for the job because it says, Only invited users can do it.

    Screen.Recording.1405-03-10.at.12.26.13.PM.mov
  18. nabi-ebrahimi commented on May 31, 2026

    @nabi-ebrahimi
    Contributor

    @mallenexpensify, Accepted the offer. thx.

  19. mallenexpensify commented on Jun 1, 2026

    @mallenexpensify
    Contributor

    @nabi-ebrahimi paid, summary updated above. Thx.

    Unfortunately, I’m not able to submit a proposal for the job because it says, Only invited users can do it.

    Saw this bug last week on another issue too. Hopefully it doesn't keep happening.

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions