Button

The label. It is wrapped in a `Text` that inherits, so it takes the button's own type instead of imposing paragraph type on it.

The scale the variant draws from. Name the scale and let the variant pick the steps out of it; pinning a step here is what breaks the hover and active states, which are derived from it.

The element it renders. With anything other than `button` — an `a` for a CTA that navigates, a router `Link` — React Aria adds the `role`, the `tabIndex` and the Space and Enter handling, so the keyboard contract does not degrade. The `type` is only written when the element is a button.

Blocks the press and drops the hover and press animation with it. No need to pair it with `loading`, which already disables on its own.

Stretches the button to its container instead of hugging the label.

Overrides the glass step the variant's recipe asks for. It is ignored in three cases that are not errors: a variant whose recipe has no glass, a theme with `effects.glass.enabled` off, and a `color` that is not one of the theme's scales — a hex or a role path never takes glass.

Read only by `variant="gradient"`, where it replaces the theme's pair. `deg` is 135 if you do not say otherwise, and `animate` needs this override to exist at all — it does nothing over the theme's own gradient.

Only has an effect with `component`: these are the attributes of the element you chose.

An adornment before the label. It is `aria-hidden`, so it can only ever repeat what the label already says — an icon that carries meaning of its own belongs in the label.

Lays a spinner over the button, marks it `aria-busy` and disables it. Label and sections dim in place instead of being removed, so the button holds its width while the work runs.

The same after the label, and `aria-hidden` for the same reason.

The control's height and padding. The label does not carry its own type scale — it inherits the button's — so this is the one step that resizes the whole thing.

The recipe the theme resolves background, border, glow and glass from, all at once. It is the variant and not `color` that decides how loudly the button reads, so a secondary action stays secondary whatever scale you tint it with.