update: Scrollable feature training modal styles to support narrow layout

[samranahm]

Explanation of Change

Fixed Issues

$ #78597
PROPOSAL: #78597 (comment)

Tests

Precondition:

• Migrate from Old Dot to New Dot or enter the below code in terminal
  Onyx.merge('nvp_tryNewDot', {nudgeMigration: {timestamp: Date.now()}})

OR

• Open any modal using deep link

https://dev.new.expensify.com:8082/auto-submit
https://dev.new.expensify.com:8082/onboarding/explanation
https://dev.new.expensify.com:8082/onboarding/migrated-user-welcome
https://dev.new.expensify.com:8082/onboarding/test-drive
https://dev.new.expensify.com:8082/change-workspace-educational
https://dev.new.expensify.com:8082/track-training

Test:

1. Open the app on desktop web, open DevTools, and reduce the viewport height and width to enable the Narrow Layout.
2. Scroll the modal and verify that it is easily scrollable.
3. Open the modals on small screens and verify that the modal is scrollable when the viewport is small.

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// 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 verified there are no new alerts related to the canBeMissing param for useOnyx
• 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

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

macOS.Chrome.mov

[Copilot]

Pull request overview

This PR fixes a scrolling issue in the Feature Training Modal (including the "Welcome to New Expensify" banner) on mobile and narrow layouts by applying a maximum height constraint to enable proper scrolling.

Key Changes:

• Added a new shouldUseMaxHeight parameter to getScrollableFeatureTrainingModalStyles to apply maxHeight: '100dvh' on narrow layouts
• Updated FeatureTrainingModal to pass the shouldUseNarrowLayout flag to the style utility function

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/styles/utils/index.ts	Added shouldUseMaxHeight parameter to getScrollableFeatureTrainingModalStyles function to enable maxHeight constraint on narrow layouts in addition to mobile Chrome
src/components/FeatureTrainingModal.tsx	Passes shouldUseNarrowLayout to the style utility function and updates useMemo dependencies accordingly

---

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

[Copilot]

The new scrolling behavior for narrow layouts is not covered by tests. Consider adding a test case that verifies the shouldUseScrollView prop works correctly with shouldUseNarrowLayout and that the appropriate styles are applied when the modal is rendered in a narrow layout. This would help ensure the scrolling fix for the migration modal works as expected across different viewport sizes.

[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/components/FeatureTrainingModal.tsx	85.71% <100.00%> (ø)
src/styles/utils/index.ts	49.41% <0.00%> (-0.08%)	⬇️
... and 8 files with indirect coverage changes

[situchan]

Upon checking QA video, it is not feature training modal which was out of scope. What did you fix though?

[samranahm]

The issue indeed not within the scope of ours. So, should we ask QA to create a separate issue with clear requirements and expectations.

[samranahm]

Well this change enables scrolling on web when the modal is rendered in a narrow layout.