FullScreenModalLayout

Components/Overlays/FullScreenModalLayout

Interactive docs page: https://wix-pages.com/design-system-documentation/#/component/fullscreenmodallayout

Overview

Copy

FullScreenModalLayout is a mobile first layout used for push screens and full screen modals inside native looking flows.

It takes over the whole viewport, with an optional header, scrollable content, and an optional sticky footer.

Do

  • Use for focused tasks that need the user's full attention (create, edit, review).
  • Use for flows that feel like a new screen in the app, not just a small dialog.
  • Use the <FullScreenModalLayout.Header/> for page level actions like back, close, save, done.
  • Use the <FullScreenModalLayout.Footer/> for primary actions that should always stay visible (for example "Save", "Continue").

Don't

  • Do not use on desktop. Use <CustomModalLayout/>, <AnnouncementModalLayout/>, <MessageModalLayout/> instead
  • Do not stack multiple full screen modals on top of each other.
  • Do not turn it into a generic container for everything. If content feels like a long page, consider using a regular page instead.

Feature examples

Structure

FullScreenModalLayout is built from three components:

  • FullScreenModalLayout.Header
  • FullScreenModalLayout.Content
  • FullScreenModalLayout.Footer
Copy

Animation

Control FullScreenModalLayout animation styles using Modal transition property:

zoomIn (default) - the modal appears from the middle of the screen

  • moveVertical - the modal slides in from the bottom
  • moveHorizontal - the modal slides in from the right side of the screen
Copy

Common use case examples

Long forms

It is recommended to use FullScreenModalLayout.Footer for modals that are longer. This way the main actions are always visible to users

Copy

Push screens

You can use FullScreenModalLayout as push screens

Copy

Multiple actions

Copy

Code

Copy

Props

NameTypeDefaultDescription
childrenReactNode—Renders modal content.
dataHookstring—Applies a data-hook HTML attribute to be used in the tests.
styleCSSProperties—

Testkit

Import the driver matching your test environment:

Copy

Driver methods

MethodDescription
getHeaderTextGets the header text
getContentTextGets the content text
getFooterTextGets the footer text
existsChecks whether the component found with the given data hook.
elementGets the component root element.
clickClicks on the component root element.
baseReturns UniDriver for the base element.

Changelog

  • 1.344.0 (2026-10-28) — maintenance release, no component-specific changes
  • 1.340.0 (2026-10-21) — maintenance release, no component-specific changes
  • 1.339.0 (2026-10-19) — maintenance release, no component-specific changes
  • 1.338.0 (2026-10-15) — maintenance release, no component-specific changes
  • 1.331.0 (2026-10-01) — maintenance release, no component-specific changes
  • 1.330.0 (2026-09-28) — maintenance release, no component-specific changes
  • 1.325.0 (2026-09-17) — maintenance release, no component-specific changes
  • 1.322.0 (2026-09-09) — maintenance release, no component-specific changes
  • 1.310.0 (2026-08-10) — maintenance release, no component-specific changes
  • 1.305.0 (2026-07-28) — maintenance release, no component-specific changes
  • 1.292.0 (2026-06-22) — maintenance release, no component-specific changes
  • 1.291.0 (2026-06-19) — maintenance release, no component-specific changes
  • 1.271.0 (2026-04-22) — maintenance release, no component-specific changes
  • 1.266.0 (2026-04-07) — maintenance release, no component-specific changes
  • 1.260.0 (2026-03-17) — maintenance release, no component-specific changes
  • 1.225.0 (2025-11-07) — feat: add initial implementation (#15464)

Last updated: 30 October 2026

Did this help?