Modal

The modal component provides a solid foundation for creating dialogs, popovers, lightboxes, or whatever else.

The component renders its children node in front of a backdrop component. The Modal offers important features:

💄 Manages modal stacking when one-at-a-time just isn't enough.
🔐 Creates a backdrop, for disabling interaction below the modal.
🔐 It disables scrolling of the page content while open.
♿️ It properly manages focus; moving to the modal content, and keeping it there until the modal is closed.
♿️ Adds the appropriate ARIA roles automatically.

Terminology note. The term "modal" is sometimes used to mean "dialog", but this is a misnomer. An element is considered modal if it blocks interaction with the rest of the application. A modal window describes parts of a UI.

If you are creating a modal dialog, you probably want to use the Dialog component rather than directly using Modal. Modal is a lower-level construct that is leveraged by the following components:

<Button onClick={handleOpen}>Open modal</Button>
<Modal
  open={open}
  onClose={handleClose}
  aria-labelledby="modal-modal-title"
  aria-describedby="modal-modal-description"
>
  <Box sx={style}>
    <Typography id="modal-modal-title" variant="h6" component="h2">
      Text in a modal
    </Typography>
    <Typography id="modal-modal-description" sx={{ mt: 2 }}>
      Duis mollis, est non commodo luctus, nisi erat porttitor ligula.
    </Typography>
  </Box>
</Modal>

Notice that you can disable the outline (often blue or gold) with the outline: 0 CSS property.

Unstyled

📦 4.7 kB comprimido

The modal also comes with an unstyled version. It's ideal for doing heavy customizations and minimizing bundle size.

import ModalUnstyled from '@material-ui/unstyled/ModalUnstyled';

<button type="button" onClick={handleOpen}>
  Open modal
</button>
<StyledModal
  aria-labelledby="unstyled-modal-title"
  aria-describedby="unstyled-modal-description"
  open={open}
  onClose={handleClose}
  BackdropComponent={Backdrop}
>
  <Box sx={style}>
    <h2 id="unstyled-modal-title">Text in a modal</h2>
    <p id="unstyled-modal-description">Aliquid amet deserunt earum!</p>
  </Box>
</StyledModal>

Modals can be nested, for example a select within a dialog, but stacking of more than two modals, or any two modals with a backdrop is discouraged.

<Button onClick={handleOpen}>Open modal</Button>
<Modal
  open={open}
  onClose={handleClose}
  aria-labelledby="parent-modal-title"
  aria-describedby="parent-modal-description"
>
  <Box sx={{ ...style, width: 400 }}>
    <h2 id="parent-modal-title">Text in a modal</h2>
    <p id="parent-modal-description">
      Duis mollis, est non commodo luctus, nisi erat porttitor ligula.
    </p>
    <ChildModal />
  </Box>
</Modal>

Transiciones

The open/close state of the modal can be animated with a transition component. Este componente debe respetar las siguientes condiciones:

Ser un hijo directo del modal.
Have an in prop. This corresponds to the open/close state.
Call the onEnter callback prop when the enter transition starts.
Call the onExited callback prop when the exit transition is completed. These two callbacks allow the modal to unmount the child content when closed and fully transitioned.

Modal has built-in support for react-transition-group.

Como alternativa, puedes usar react-spring.

Rendimiento

The content of modal is unmounted when closed. If you need to make the content available to search engines or render expensive component trees inside your modal while optimizing for interaction responsiveness it might be a good idea to change this default behavior by enabling the keepMounted prop:

<Modal keepMounted />

As with any performance optimization, this is not a silver bullet. Be sure to identify bottlenecks first, and then try out these optimization strategies.

React doesn't support the createPortal() API on the server. In order to display the modal, you need to disable the portal feature with the disablePortal prop:

Limitaciones

Focus trap

The modal moves the focus back to the body of the component if the focus tries to escape it.

This is done for accessibility purposes. However, it might create issues. In the event the users need to interact with another part of the page, e.g. with a chatbot window, you can disable the behavior:

<Modal disableEnforceFocus />

Accesibilidad

(WAI-ARIA: https://www.w3.org/TR/wai-aria-practices/#dialog_modal)

Be sure to add aria-labelledby="id...", referencing the modal title, to the Modal. Additionally, you may give a description of your modal with the aria-describedby="id..." prop on the Modal.

<Modal
  aria-labelledby="modal-title"
  aria-describedby="modal-description"
  >
  <h2 id="modal-title">
    My Title
  </h2>
  <p id="modal-description">
    My Description
  </p>
  </Modal>

The WAI-ARIA authoring practices can help you set the initial focus on the most relevant element, based on your modal content.
Windows under a modal are inert. Keep in mind that a "modal window" overlays on either the primary window or another modal window. Keep in mind that a "modal window" overlays on either the primary window or another modal window. This might create conflicting behaviors.