Choose a version:

Modal

The modal component displays content in an overlay. Use to create a distraction-free experience such as a confirmation dialog or a settings panel.

Modals support a heading, scrollable body content, and action slots for primary and secondary buttons. For contextual content that doesn't require full focus, use popover instead.

Only one modal is visible at a time — triggering a second modal while another is open replaces the first without stacking. Modals open in response to buyer interaction only, not programmatically on page load.

Support

Targets (29)

Supported targets

Anchor to PropertiesProperties

Configure the following properties on the modal component.

Anchor to accessibilityLabel accessibilityLabel string: A label that describes the purpose of the modal, announced by assistive technologies. When set, screen readers will use this label instead of the heading to describe the modal.
Anchor to heading heading string: A title that describes the content of the modal.
Anchor to id id string: A unique identifier for the element. Use this to reference the element in JavaScript, link labels to form controls, or target specific elements for styling or scripting.
Anchor to padding padding 'base' | 'none' Default: 'base': Adjust the padding around the modal content.

base: Applies padding that is appropriate for the element.

none: Removes all padding from the element. This can be useful when elements inside the modal need to span to the edge of the modal. For example, a full-width image. In this case, rely on box with a padding of base to bring back the desired padding for the rest of the content.
Anchor to size size 'small' | 'large' | 'base' | 'small-100' | 'large-100' | 'max' Default: 'base': The size of the modal.

'base': The default size, suitable for most use cases.

'small': A compact modal for simple confirmations or short messages.

'small-100': The smallest modal size.

'large': A large modal for complex content or forms.

'large-100': The largest fixed-size modal, providing maximum room for content.

'max': Expands the modal to its maximum size as defined by the host application, on both the horizontal and vertical axes.

Anchor to EventsEvents

The modal component provides event callbacks for handling user interactions. Learn more about handling events.

Anchor to afterhide afterhide <typeof tagName>: A callback fired when the modal is hidden, after any hide animations have completed.
Anchor to aftershow aftershow <typeof tagName>: A callback fired when the modal is shown, after any show animations have completed.
Anchor to hide hide <typeof tagName>: A callback fired immediately after the modal is hidden.
Anchor to show show <typeof tagName>: A callback fired immediately after the modal is shown.

CallbackEventListener

A typed event listener for custom element events. The listener receives a `CallbackEvent` with the correct `currentTarget` type for the associated custom element tag.

(EventListener & {
    (event: CallbackEvent<TTagName, Event> & TData): void;
}) | null

CallbackEvent

An event type that narrows the `currentTarget` to the specific HTML element associated with the custom element tag. This provides type-safe event handling in callback listeners.

TEvent & {
    currentTarget: HTMLElementTagNameMap[TTagName];
}

Anchor to SlotsSlots

The modal component supports slots for additional content placement within the component. Learn more about using slots.

Anchor to primary-action primary-action HTMLElement: The main action button displayed in the modal footer, representing the primary action users should take. Only accepts a single button component.
Anchor to secondary-actions secondary-actions HTMLElement: Additional action buttons displayed in the modal footer, providing alternative or supporting actions.

Anchor to MethodsMethods

The modal component exposes methods for programmatic control. Learn more about using methods.

Anchor to hideOverlay hideOverlay () => void required: A method to programmatically hide the overlay and run any associated hide animations.

Anchor to ExamplesExamples

Anchor to Display a return policyDisplay a return policy

Show store policy details without leaving the checkout page. This example opens a modal with return policy text and a close button.

Display a return policy

A rendered example of the modal component

html

<s-button command="--show" commandFor="modal-1">Add Product</s-button>

<s-modal id="modal-1" heading="Return Policy">

<s-paragraph>

We have a 30-day return policy, which means you have 30 days after receiving

your item to request a return.

</s-paragraph>

<s-paragraph>

To be eligible for a return, your item must be in the same condition that

you received it, unworn or unused, with tags, and in its original packaging.

You’ll also need the receipt or proof of purchase.

</s-paragraph>

<s-button

variant="primary"

command="--hide"

commandFor="modal-1"

slot="primary-action"

</s-button>

</s-modal>

Anchor to Confirm a destructive actionConfirm a destructive action

Ask buyers to confirm before cancelling an order or removing an item. This example uses a small modal with a warning, a critical-toned confirm button, and a cancel button.

html

<s-stack gap="base">

<s-button tone="critical" command="--show" commandFor="delete-modal">

Cancel order

</s-button>

<s-modal id="delete-modal" heading="Cancel this order?" size="small">

<s-stack>

<s-text>Are you sure you want to cancel order #1042?</s-text>

<s-text tone="warning">

This will release all reserved inventory. This action cannot be undone.

</s-text>

</s-stack>

<s-button

slot="primary-action"

variant="primary"

tone="critical"

command="--hide"

commandFor="delete-modal"

Cancel order

</s-button>

<s-button

slot="secondary-actions"

variant="secondary"

command="--hide"

commandFor="delete-modal"

Keep order

</s-button>

</s-modal>

</s-stack>

Anchor to Collect input with a formCollect input with a form

Collect buyer input without leaving the checkout page. This example shows a gift message form with text fields, a text area, a checkbox, and save and cancel buttons.

html

<s-stack gap="base">

<s-button command="--show" commandFor="gift-modal">

Add gift message

</s-button>

<s-modal id="gift-modal" heading="Gift message" size="base">

<s-stack>

<s-text-field label="Recipient name" required></s-text-field>

<s-text-area label="Message" rows="3" maxLength="200"></s-text-area>

<s-checkbox label="Include gift receipt"></s-checkbox>

</s-stack>

<s-button

slot="primary-action"

variant="primary"

command="--hide"

commandFor="gift-modal"

Save message

</s-button>

<s-button

slot="secondary-actions"

variant="secondary"

command="--hide"

commandFor="gift-modal"

Cancel

</s-button>

</s-modal>

</s-stack>

Anchor to Best practicesBest practices

Use for focused, specific tasks: Modals work best when buyers need to make a decision or acknowledge critical information. Don't use them for contextual tools or actions that could happen on the page directly.
Write clear headings: Use concise titles that communicate the purpose of the modal, such as "Cancel this order?" or "Gift message."
Size appropriately: Use small for simple confirmations and base for forms or longer content. Avoid oversized modals for short messages.
Include a prominent call to action: Every modal should have a clear primary action so buyers know what to do next. Always include a secondary action or dismiss mechanism so buyers aren't trapped in the overlay.
Use critical tone for destructive actions: Set tone="critical" on the primary button when the action is irreversible, like cancelling an order. Describe what'll happen in the modal body before the buyer confirms.
Use specific action verbs: Label buttons with clear verbs like "Cancel order", "Save", or "Continue" rather than vague terms like "Yes", "OK", or "Submit."
Don't nest modals: Avoid launching one modal from another. If the workflow requires multiple steps, reconsider the design.
Use sparingly: Don't create unnecessary interruptions. Modals should be a last resort for important decisions during checkout.

Was this page helpful?