Button

Use button for the main actions on a page or form.
  • Alpha
  • Not reviewed for accessibility
This documentation is moving to a new home. Please update any link or bookmark that points to this page. The new content can be found here.
import {Button} from '@primer/react'

Examples

Default button

This is the default variant for the Button component.

Danger button

The danger variant of Button is used to warn users about potentially destructive actions

Invisible button

The invisible variant of Button indicates that the action is a low priority one.

Different sized buttons

Button component supports three different sizes. small, medium, large.

Appending an icon

We can place an icon inside the Button in either the leading or the trailing position to enhance the visual context. It is recommended to use an octicon here.

Icon only button

A separate component called IconButton is used if the action shows only an icon with no text. This button will remain square in shape.

Different sized icon buttons

IconButton also supports the three different sizes. small, medium, large.

Button with counter

To show a count value as a trailing visual inside Button, pass a value to the count prop. The counter will match the variant styles of the parent button.

Block button

Use the block prop for full width buttons.

Props

Button

NameTypeDefaultDescription
alignContent
'start' | 'center'

Content alignment for when visuals are present.

as
React.ElementType
'button'

The underlying element to render — either a HTML element name or a React component.

block
boolean

Allow button width to fill its container.

children Required
React.ReactNode

The content of the button.

count
number | string

For counter buttons, the number to display.

disabled
boolean

Items that are disabled can not be clicked, selected, or navigated through.

inactive
boolean

Whether the button looks visually disabled, but can still accept all the same interactions as an enabled button. This is intended to be used when a system error such as an outage prevents the button from performing its usual action. Inactive styles are slightly different from disabled styles because inactive buttons need to have an accessible color contrast ratio. This is because inactive buttons can have tooltips or perform an action such as opening a dialog explaining why it's inactive. If both disabled and inactive are true, disabled takes precedence.

leadingIcon Deprecated
React.ComponentType<OcticonProps>

An icon to display before the button text.

leadingVisual
React.ElementType

A visual to display before the button text.

ref
React.RefObject<HTMLButtonElement>
size
'small'
| 'medium'
| 'large'
'medium'
sx
SystemStyleObject
trailingIcon Deprecated
React.ComponentType<OcticonProps>

An icon to display after the button text.

trailingVisual
React.ElementType

A visual to display after the button text.

variant
'default'
| 'primary'
| 'danger'
| 'invisible'
'default'

Change the visual style of the button.

Additional props are passed to the <button> element. See button docs for a list of props accepted by the <button> element.

Status

Alpha

  • Component props and basic example usage of the component are documented on primer.style/react.
  • Component does not have any unnecessary third-party dependencies.
  • Component can adapt to different themes.
  • Component can adapt to different screen sizes.
  • Component has robust unit test coverage (100% where achievable).
  • Component has visual regression coverage of its default and interactive states.
  • Component does not introduce any axe violations.
  • Component has been manually reviewed by the accessibility team and any resulting issues have been addressed.

Beta

  • Component is used in a production application.
  • Common usage examples are documented on primer.style/react.
  • Common usage examples are documented in storybook stories.
  • Component has been reviewed by a systems designer and any resulting issues have been addressed.
  • Component does not introduce any performance regressions.

Stable

  • Component API has been stable with no breaking changes for at least one month.
  • Feedback on API usability has been sought from developers using the component and any resulting issues have been addressed.
  • Component has corresponding design guidelines documented in the interface guidelines.
  • Component has corresponding Figma component in the Primer Web library.
  • Tooling (such as linters, codemods, etc.) exists to prevent further use of alternatives.