Skip to main content

Button

The button component triggers actions or events, such as submitting forms, opening dialogs, or navigating to other pages. Use buttons to let buyers perform specific tasks or initiate interactions throughout the interface.

Buttons support various visual styles, tones, and interaction patterns to communicate intent and hierarchy. They can also function as links, guiding buyers to internal or external destinations. For navigation-focused interactions within text, use link. For grouping multiple related buttons, use button group.

Support
Targets (29)

Configure the following properties on the button component.

Anchor to accessibilityLabel
accessibilityLabel
string

A label that describes the purpose or content of the button for users of assistive technologies such as screen readers. Use this when the visible content alone doesn't provide enough context.

Anchor to command
command
'--auto' | '--show' | '--hide' | '--toggle' | '--copy'
Default: '--auto'

Sets the action the commandFor target should take when this component is activated. Available options:

  • '--auto': Performs the default action appropriate for the target component.
  • '--show': Displays the target component if it's currently hidden.
  • '--hide': Conceals the target component from view.
  • '--toggle': Alternates the target component between visible and hidden states.
  • '--copy': Copies the target clipboard item.

The supported actions vary by target component type. Learn more about the command attribute.

Anchor to commandFor
commandFor
string

The ID of the component to control when this component is activated. Pair with the command property to specify what action to perform on the target component. Learn more about the commandFor attribute.

When both commandFor and href are set, commandFor takes precedence. The command runs and the link doesn't navigate.

Anchor to disabled
disabled
boolean
Default: false

Whether the button is disabled, preventing it from being clicked or receiving focus.

string

The URL to navigate to when clicked. The click event fires first, then navigation occurs. If commandFor is also set, the command executes instead of navigation.

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 inlineSize
inlineSize
'auto' | 'fill' | 'fit-content'
Default: 'auto'

The inline width of the button component.

  • 'auto': The size depends on the surface and context.
  • 'fill': The button takes up 100% of the available inline size.
  • 'fit-content': The button takes up the minimum inline size required to fit its content.
Anchor to interestFor
interestFor
string

The ID of the component to show when users hover over or focus on this component. Pair with a target component that supports interest-based interactions. Learn more about the interestFor attribute.

Anchor to loading
loading
boolean
Default: false

Whether the button is in a loading state, which replaces the button content with a loading indicator while a background action is being performed. This also disables the button.

Anchor to target
target
'auto' | '_blank'
Default: 'auto'

Specifies where to display the linked URL. Learn more about the target attribute.

  • 'auto': Opens the URL in the current frame or a new tab, depending on the context.
  • '_blank': Opens the URL in a new tab or window.
'auto' | 'neutral' | 'critical'
Default: 'auto'

The semantic meaning and color treatment of the button.

  • 'auto': Automatically determined based on context.
  • 'neutral': General information without specific intent.
  • 'critical': Urgent problems or destructive actions.
'submit' | 'button'
Default: 'button'

The behavioral type of the button component, which determines what action it performs when activated.

  • submit: Submits the nearest containing form.
  • button: Performs no default action, relying on the click event handler for behavior.

This property is ignored if href or commandFor/command is set.

Anchor to variant
variant
'auto' | 'primary' | 'secondary'
Default: 'auto'

The visual style variant of the button component, which controls its prominence and emphasis.

  • 'auto': Automatically determined by the button's context.
  • 'primary': High-emphasis style for the main action.
  • 'secondary': Medium-emphasis style for supporting actions.
  • 'tertiary': Low-emphasis style for less prominent actions.

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

Anchor to click
click
<typeof tagName>

A callback fired when the button is clicked. This will be called before the action indicated by type.

Learn more about the click event.


Anchor to Add primary and secondary buttonsAdd primary and secondary buttons

Create a save and cancel button pair to highlight the primary action. This example shows two s-button elements with variant set to primary and secondary.

Add primary and secondary buttons

A rendered example of the button component

html

<s-button variant="secondary">Cancel</s-button>
<s-button variant="primary">Save</s-button>

Anchor to Show a loading stateShow a loading state

Prevent duplicate submissions by showing a loading indicator while an operation completes. This example displays buttons with the loading attribute across primary and secondary variants.

html

<!-- Payment processing -->
<s-button loading variant="primary">Placing order...</s-button>

<!-- Discount validation -->
<s-button loading variant="secondary">Applying code...</s-button>

Anchor to Open an external pageOpen an external page

Navigate to an external page by adding the href attribute to a button. This example renders an s-button with href and target="_blank" to open the destination in a new tab.

html

<s-button href="https://www.shopify.com" target="_blank">Visit our store</s-button>

  • Write action-oriented text: Use specific, actionable language like "Apply discount" or "Save preferences" rather than vague terms like "OK" or "Click here."
  • Choose appropriate variants: Use primary for the main action and secondary for supporting actions. Limit each context to one primary button.
  • Show loading states: Set loading to true during async operations to prevent duplicate submissions and provide visual feedback.
  • Structure hierarchies clearly: Group related actions together. Use tone="critical" for destructive actions to prevent accidental activation.

Was this page helpful?