You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-05-29] [$250] DEV : Unable to scroll in "More" bottom sheet of expenses #86593
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:
Go to reports tab.
Open any expense which is in draft state.
Click on "More".
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:
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)
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.
Auto-detect overflow and conditionally enable ScrollView based on item count — More elegant but adds complexity for a straightforward fix.
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.
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
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
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
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
⚠️@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.
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
@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.
Activity
MelvinBot commentedon Mar 28, 2026
Proposal
What is the root cause of that problem?
The
PopoverMenucomponent defaultsshouldUseScrollViewtofalse(PopoverMenu.tsx:297). When the "More" button is tapped on an expense,MoneyRequestHeaderSecondaryActionsrenders aButtonWithDropdownMenuwithout passingshouldPopoverUseScrollView={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_DOCKEDmodal withoverflow: 'hidden'on its container (ModalStyleUtils.ts:234), and the inner content has amaxHeightof 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 plainView(not aScrollView), 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}fromMoneyRequestHeaderSecondaryActionstoButtonWithDropdownMenu. This enablesPopoverMenuto 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)
shouldUseScrollViewtotrueinPopoverMenu— This would fix the issue globally but could have unintended side effects on popover measurement logic in other callers that don't need scrolling.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 thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.melvin-bot commentedon Mar 28, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @FitseTLT (
External)melvin-bot commentedon Mar 28, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022037692302907449843
[-]DEV : Unable to scroll in "More" bottom sheet of expenses[/-][+][$250] DEV : Unable to scroll in "More" bottom sheet of expenses[/+]Coincatcher commentedon Mar 28, 2026
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: autoinside bottom sheet modals that useposition: fixedor 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
BottomSheetcomponent likely usesreact-native-reanimatedor a similar library withtransform: 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 innerScrollView.What changes do you think we should make in order to fix the problem?
Fix: Add
-webkit-overflow-scrolling: touchand proper touch handling for iOS mWebIn the bottom sheet content wrapper (likely in
src/components/BottomSheet/orsrc/components/Popover/), add platform-specific styling for web:-webkit-overflow-scrolling: touchon the scrollable content areaoverscroll-behavior: containto prevent scroll chaining to the parenttouch-action: pan-yis set on the scrollable contentIf 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 > 0before allowing downward pan).Files to modify:
src/components/PopoverMenu/index.tsxor the bottom sheet content wrapperlayacat commentedon Mar 28, 2026
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
shouldPopoverUseScrollViewhere:App/src/components/MoneyRequestHeaderSecondaryActions.tsx
Lines 501 to 510 in 6b17cfc
===> Our
ButtonWithDropdownMenucontent 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
shouldPopoverUseScrollViewwhen ourapplicableSecondaryActionsreaches the threadhold like we did in other places.sayanget commentedon Mar 28, 2026
🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.
melvin-bot commentedon Mar 28, 2026
✅ Contributor details stored successfully. Thank you for contributing to Expensify!
github-actions commentedon Mar 28, 2026
52 remaining items
melvin-bot commentedon May 28, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mallenexpensify commentedon May 29, 2026
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
nabi-ebrahimi commentedon May 31, 2026
@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
nabi-ebrahimi commentedon May 31, 2026
@mallenexpensify, Accepted the offer. thx.
mallenexpensify commentedon Jun 1, 2026
@nabi-ebrahimi paid, summary updated above. Thx.
Saw this bug last week on another issue too. Hopefully it doesn't keep happening.