easeul

No libraryTransitions

Native popover

Light dismissed by the browser. The exit plays while the element is still in the top layer, which is the part a naive implementation gets wrong.

Every value the manifest allows on this host, single presets and the pairs that compose. The first is what this component ships with. Both stages are the same component, so anything that changes between them is the attribute.

withoutno attribute
with easefuldata-motion="scale-fade"
host writes

:popover-open, and the top layer

easeful matches

[data-motion~="scale-fade"][popover]:not(:popover-open)

what runs

transition: opacity, scale, display, overlay

you write

<div popover data-motion="scale-fade">

Where the attribute goes

The parts this demo composes, and the value each one carries. Everything inside an animated part is that part's content, so the tree stops there.

  1. button
  2. divdata-motion="scale-fade"

Source

"use client"

import { useId } from "react"
import type { DemoProps } from "@/components/demos/props"

export function NativePopover({ motion }: DemoProps) {
  const id = useId()

  return (
    <>
      <button type="button" className="btn" popoverTarget={id}>
        Open popover
      </button>
      <div id={id} popover="auto" className="modal" data-motion={motion}>
        <p className="panel__title">Light dismissed by the browser</p>
        <p className="panel__body">
          Click outside or press Escape. The exit plays while the element is still in the top
          layer, which is the part a naive implementation gets wrong.
        </p>
        <div className="modal__actions">
          <button
            type="button"
            className="btn btn--primary"
            popoverTarget={id}
            popoverTargetAction="hide"
          >
            Close
          </button>
        </div>
      </div>
    </>
  )
}
The whole file, read from disk at build time. Both copies above render from it, and the motion prop is the only difference between them.