fix: defer BOTTOM_DOCKED modal open until keyboard dismissed on mobile web

[neerajbachani]

Explanation of Change

When a user taps the three-dot menu while the software keyboard is open on mobile web, the bottom-docked modal ("Remove" option) was rendering while the keyboard was still animating closed. This caused a large blank space above the menu item for ~300-400ms (the keyboard animation duration).

Root cause: In ThreeDotsMenu/index.tsx, onIconPress?.() (which calls blurActiveElement() + KeyboardUtils.dismiss()) was called AFTER showPopoverMenu(), so the modal opened before the keyboard started dismissing.

Two targeted fixes:

1. src/components/ThreeDotsMenu/index.tsx

• Moved onIconPress?.() to fire BEFORE showPopoverMenu() so keyboard dismissal starts immediately
• Wrapped menu open in KeyboardUtils.dismiss().then(openMenu) using the existing project utility resolves immediately if keyboard is not open, waits for full dismissal if it is. Works correctly on both iOS Safari and Android Chrome.

2. src/styles/utils/generators/ModalStyleUtils.ts

• Expanded guard from isMobileSafari() to isMobile() - interactive-widget=resizes-content is Chrome-only; Android Firefox, Samsung Internet, and older Android Chrome also ignore it and have the same window.innerHeight stability issue
• Added height: 'fit-content' alongside maxHeight so the modal container collapses to actual content size instead of expanding to fill maxHeight. Preserves original PR Fix test drive modal not moving when keyboard openes #62799 behavior for large modals (content larger than viewport still scrolls correctly).

Fixed Issues

$ #86639
PROPOSAL: #86639 (comment)

Tests

1. Go to staging.new.expensify.com on iOS Safari (mWeb)
2. Go to Account > Profile > Contact methods
3. Tap New contact method, enter email, tap Add
4. On magic code page, tap the input to open the keyboard
5. Tap the 3-dot menu (top right)
6. Verify: modal appears immediately with no blank space above "Remove" ✓
7. Verify: "Remove" option is visible and tappable ✓
8. Repeat steps 4-7 on Android Chrome (mWeb)
9. Verify: same behavior, no blank space ✓
10. Tap 3-dot menu WITHOUT keyboard open - verify menu opens immediately
    with no delay ✓
11. Verify other ThreeDotsMenu usages elsewhere in app are not affected

• Verify that no errors appear in the JS console

Offline tests

1. Follow preconditions above
2. Disable network, tap the input to open keyboard, tap 3-dot menu
3. Verify modal opens correctly with no blank space
4. Re-enable network and verify normal behavior

• Verify that no errors appear in the JS console

QA Steps

Same as Tests section above.

• 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: mWeb Chrome

andoid-preview.mp4

iOS: Native

iOS: mWeb Safari

ios-safari-preview.mp4

MacOS: Chrome / Safari

[melvin-bot]

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

[neerajbachani]

Checklist Notes

• Screenshots - Android/iOS Native: N/A - fix is mWeb only, no native code changed
• Localization: N/A - no new user-facing text added
• Unit tests: N/A - timing/browser behavior not unit testable in isolation
• Storybook: N/A - no component stories modified
• Design label: N/A - no UI layout changes
• Deeplink: N/A - no new pages or deeplink routes added
• New assets: N/A - no assets added or modified
• High Traffic account: Tested against staging API ✓

[shawnborton]

I think the video looks good to me? Might be nice to see a very clear side-by-side before and after video?

[brunovjk]

@neerajbachani It seems I've encountered a regression; the 3-dot menu no longer appears in the web (Chrome):

Screen.Recording.2026-04-06.at.11.51.02.mov

Can you reproduce it as well? Thank you.

[joekaufmanexpensify]

Good for product 👍

[neerajbachani]

Hi @brunovjk, thanks for catching that! The issue was that KeyboardUtils.dismiss().then(openMenu) was unconditional even on desktop where the Promise resolves immediately, .then() still defers openMenu to the microtask queue, which broke the click/focus event sequencing.

Fixed by guarding with isMobile(): desktop now calls openMenu() synchronously (same as the original code), while mobile web still waits for the keyboard to fully close before opening the menu.

Could you re-test on desktop Chrome when you get a chance? Thanks!

[neerajbachani]

Thanks @shawnborton @joekaufmanexpensify @brunovjk for the review! Here's a side-by-side video comparing staging (left) vs the fix (right) - no blank space on mobile web, and the desktop regression is resolved too.

lv_0_20260408142720.mp4

[joekaufmanexpensify]

LGTM, as long as design is cool with it 👍

[brunovjk]

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

Android: mWeb Chrome

87143_android_web.mov

iOS: HybridApp

iOS: mWeb Safari

87143_ios_web.mov

MacOS: Chrome / Safari

87143_web_chrome.mov

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/styles/utils/generators/ModalStyleUtils.ts	35.38% <100.00%> (ø)
src/components/ThreeDotsMenu/index.tsx	88.88% <0.00%> (-2.03%)	⬇️
... and 327 files with indirect coverage changes

[OSBotify]

✋ 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]

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

[github-actions]

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

Android 🤖	iOS 🍎
❌ FAILED ❌	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-629091f-378883a-bc22849ec0823393723be06a16b7c47fb05a4dfc/index.html
The QR code can't be generated, because the Android build failed

Web 🕸️
https://87143.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/rlinoz in version: 9.3.55-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[MelvinBot]

No help site changes are required for this PR.

This is a UI bug fix for mobile web (blank-space flash when opening the three-dot menu while the keyboard is open). The changes are purely internal rendering fixes — keyboard dismissal timing in ThreeDotsMenu and a CSS guard expansion in ModalStyleUtils. No user-facing features, workflows, or settings are added or changed.

[IuliiaHerets]

Hi @neerajbachani. QA team failed this PR on iOS with an original issue

1775698973200.ScreenRecording_04-08-2026_20-39-53_1.mp4

cc @rlinoz @joekaufmanexpensify

[brunovjk]

Hi @neerajbachani. QA team failed this PR on iOS with an original issue

1775698973200.ScreenRecording_04-08-2026_20-39-53_1.mp4
cc @rlinoz @joekaufmanexpensify

That's odd, I tested this. @neerajbachani can you check? I'm AFK now.