DEV Community

Cover image for Your closing modal is still eating clicks
Saurabh Chauhan
Saurabh Chauhan

Posted on Originally published at beui.dev

Your closing modal is still eating clicks

You close a modal. The exit animation plays for 200ms. During those 200ms the user clicks the button behind it. Nothing happens.

The modal is fading out, so it looks gone. But it is still in the DOM, still on top, still catching the click.

This is one of the most common bugs in animated overlays, and almost every Framer Motion modal tutorial has it.

Why it happens

AnimatePresence keeps a child mounted after you remove it, so it can play the exit animation. That is the whole point. But "mounted" means the full overlay: the backdrop, the panel, the focus trap, everything.

So for the length of the exit:

  • the backdrop still covers the page and swallows pointer events
  • the dialog is still in the tab order, so focus can land in it
  • screen readers still see a dialog that is already closing

Most code gates interaction on open:

<AnimatePresence>
  {open && (
    <motion.div
      className="fixed inset-0 bg-black/40"
      style={{ pointerEvents: open ? "auto" : "none" }}
      exit={{ opacity: 0 }}
    />
  )}
</AnimatePresence>
Enter fullscreen mode Exit fullscreen mode

That check never works. When open is false, this element is not rendered with new props anymore. AnimatePresence keeps the last render, the one where open was true, and animates it out. The pointerEvents: "auto" is frozen in.

The boolean that knows

Framer Motion already tracks this. useIsPresent() returns false from the moment a child starts its exit. The catch: it only works inside the AnimatePresence subtree, one component below it.

So read it in a small child component, and pass it down:

import { useIsPresent } from "motion/react";
import type { ReactNode } from "react";

export function PresenceGate({
  children,
}: {
  children: (gate: { inert: boolean; style: { pointerEvents: "auto" | "none" } }) => ReactNode;
}) {
  const isPresent = useIsPresent();
  return children({
    inert: !isPresent,
    style: { pointerEvents: isPresent ? "auto" : "none" },
  });
}
Enter fullscreen mode Exit fullscreen mode

Then spread the gate onto every layer that takes pointer events:

<AnimatePresence>
  {open && (
    <PresenceGate>
      {(gate) => (
        <>
          <motion.div {...gate} className="fixed inset-0 bg-black/40" exit={{ opacity: 0 }} />
          <motion.div {...gate} role="dialog" aria-modal="true" exit={{ opacity: 0, y: 8 }}>
            ...
          </motion.div>
        </>
      )}
    </PresenceGate>
  )}
</AnimatePresence>
Enter fullscreen mode Exit fullscreen mode

Why inert, not just pointer-events

pointer-events: none fixes the mouse. It does nothing for the keyboard or screen readers.

inert does all three in one attribute: no pointer events, out of the tab order, hidden from the accessibility tree. An exiting dialog is not a dialog anyone should still be able to type into.

Both flip in the same commit that starts the exit. The visual exit keeps playing. The page behind is usable instantly.

The rule

Gate interaction on presence, not on open.

open tells you what the user wants. Presence tells you what is actually on screen and still in charge. During an exit those two disagree, and the page should follow the user.

Every overlay in beUI works this way: the command palette, bottom sheet and image viewer all release the page the moment they start closing. Install any of them with the shadcn CLI and the gate comes with it:

npx shadcn@latest add @beui/bottom-sheet
Enter fullscreen mode Exit fullscreen mode

Top comments (2)

Collapse
 
sunnatulla_dev profile image
Sunnatulla •

One thing to add for keyboard users: if focus is inside the dialog when inert flips (they just pressed Close or Escape), the browser drops focus to <body>. I checked in Chrome 157: inert on a dialog with its Close button focused, and activeElement was BODY by the next frame. The first Tab press after that did nothing at all.

A lot of focus-trap setups only return focus on unmount, which is after the exit finishes, so for those 200ms the keyboard user is lost. Moving focus to the trigger yourself in the close handler, before setting open to false, fixed it in the same test (focus sat on the trigger and Tab moved to the next button).

Also if anyone copies this into a React 18 app: inert as a boolean prop only works in React 19. 18 warns about a non-boolean attribute and you need inert="" instead.

Collapse
 
elias_0549e0e2ef8cf6ad89a profile image
RAMO •

The point that the frozen pointerEvents value is stuck at the last render is the part that trips most people up, I've seen that exact bug in a few codebases. One small addition on the inert approach: when the modal closes, focus should also go back to whatever opened it, and that's easy to lose if the dialog unmounts after the exit animation. Doing it when the exit starts, not when it ends, keeps keyboard users from landing on the body for 200ms. Also worth testing with prefers-reduced-motion on, since some setups skip the exit entirely and the presence gate never gets exercised. Have you found a good way to cover the in-between state in tests, or do you just check it by hand?