Skip to content
Hazine

Confirm and destructive actions

0 of 5 shipped. Nothing has shipped here yet. The list below is what this family will hold, and how each structure differs.

Planned 5

  • Inline Two-Step Confirm Button

    No overlay: confirmation happens inside the same button footprint with a reserved width to avoid layout shift, a 300ms guard against accidental double clicks, and the armed state announced through role=status.

  • Hold to Confirm Button

    Pointer hold drives a progress fill and releases early to cancel, while keyboard and single activation route to a two-button confirm popover as the non-hold alternative; under prefers-reduced-motion the fill becomes a stepped countdown label.

  • Acknowledgement Confirm Popover

    Anchored and lighter than a modal: consequences are passed as data and rendered as a required checklist, the confirm button uses aria-disabled with a hint that names how many items remain, and focus moves to the first checkbox on open.

  • Type to Confirm Field

    A text match gates the action: comparison is trimmed with a caseSensitive option, a match indicator combines icon and text, and the block is a composable fragment that can sit in a card, sheet or dialog rather than owning its own overlay.

  • Undo Window Button

    Replaces confirmation with reversal: the control itself hosts the undo affordance (no toast needed), the timer pauses on hover and focus, the commit also fires on unmount, and the window can be extended to satisfy adjustable timing.