Botão sem estilo
Buttons let users take actions and make choices with a single tap.
Introduction
ButtonUnstyled replaces the native HTML <button> element.
Component
Usage
After installation, you can start building with this component using the following basic elements:
import ButtonUnstyled from '@mui/base/ButtonUnstyled';
export default function MyApp() {
return <ButtonUnstyled>{/* button text */}</ButtonUnstyled>;
}
Basics
ButtonUnstyled behaves similarly to the native HTML <button>, so it wraps around the text that will be displayed on its surface.
The following demo shows how to create and style two basic buttons. Notice that the second button cannot be clicked due to the disabled prop:
Anatomy
The ButtonUnstyled component is composed of a root <button> slot with no interior slots:
<button class="BaseButton-root">
<!-- button text goes here -->
</button>
Slot props
Use the component prop to override the root slot with a custom element:
<ButtonUnstyled component="div" />
If you provide a non-interactive element such as a <span>, the ButtonUnstyled component will automatically add the necessary accessibility attributes.
Use the components prop to override any interior slots in addition to the root:
<ButtonUnstyled components={{ Root: 'div' }} />
Use the componentsProps prop to pass custom props to internal slots. The following code snippet applies a CSS class called my-button to the root slot:
<ButtonUnstyled componentsProps={{ root: { className: 'my-button' } }} />
Compare the attributes on the <span> in this demo with the ButtonUnstyled from the previous demo:
Hook
import { useButton } from '@mui/base/ButtonUnstyled';
The useButton hook lets you apply the functionality of ButtonUnstyled to a fully custom component. It returns props to be placed on the custom component, along with fields representing the component's internal state.
Hooks do not support slot props, but they do support customization props.
The useButton hook requires the ref of the element it's used on.
The following demo shows how to build the same buttons as those found in the Basic usage section, but with the useButton hook:
Customization
Custom elements
ButtonUnstyled accepts a wide range of custom elements beyond HTML elements. You can even use SVGs, as the following demo illustrates:
Focus on disabled buttons
Similarly to the native HTML <button> element, the ButtonUnstyled component can't receive focus when it's disabled. This may reduce its accessibility, as screen readers won't be able to announce the existence and state of the button.
The focusableWhenDisabled prop lets you change this behavior. When this prop is set, the underlying button does not set the disabled prop. Instead, aria-disabled is used, which makes the button focusable.
This should be used whenever the disabled button needs to be read by screen readers.
MUI Base uses this prop internally in menu items, making it possible to use the keyboard to navigate to disabled items (in compliance with ARIA guidelines).
The following demo shows how the focusableWhenDisabled prop works—use the Tab key to navigate within this document to see that only the second button accepts the focus:
The focusableWhenDisabled prop works the same when the root slot is customized, except that the aria-disabled attribute is used no regardless of the prop's state. The ability to receive focus is controlled internally by the tabindex attribute.