Popover

Preview

Rendered from the story the storybook (a11y) CI gate runs axe against — the preview can't show something that hasn't been verified.

Install

Two equivalent paths — the URL works in any shadcn-CLI setup; the alias works once you've registered @interlace in your components.json.

npx shadcn@latest add https://ds.interlace.tools/r/popover.json

npx shadcn@latest add @interlace/popover

Import

6 named exports — pull the parts you need.

import { MIN_VIEWPORT, Popover, PopoverAnchor, PopoverCompose, PopoverContent, PopoverTrigger } from '@/components/ui/popover';

Anatomy

Extracted from the primitive's JSDoc header. The source is the only documentation that can't drift.

Popover                          (Popover.Root + the anchor context — no DOM node of its own)
    ├─ PopoverTrigger              (Popover.Trigger)
    ├─ PopoverAnchor               (an inert div — registers itself as the positioner's anchor)
    └─ PopoverContent              (Portal → Positioner → Popup — data-min-viewport=320)
Base UI 1.6 ships no `Popover.Anchor` part; the seam is the `anchor` prop on
`Popover.Positioner`. `PopoverAnchor` therefore renders an inert element and
introduces it to `PopoverContent` through a context, so anchoring the panel
to one element while triggering it from another gives you ONE trigger. It
previously rendered a second `Popover.Trigger` under a different `data-slot`,
which gave you two.
`PopoverCompose` (also `Popover.Compose`) is the trigger + content pair in
one element for the common case.

API reference

Parsed from the type declarations in the source — the same file the install writes into your tree, so this table can't drift from the component you get.

Accessibility

Every story for this component is rendered headlessly and checked with axe-core (wcag2aa, wcag22aa, best-practice, ACT) on every PR. That gate has no continue-on-error, so what ships has zero known violations.

What follows is what static analysis can see. Axe cannot press a key and never sees an overlay open, so the operable-without-a-mouse claim lives in Behavior instead, where the keyboard path is replayed step by step.

Focus + keyboard behaviour

Owned by @base-ui/react/popover — focus trapping, dismissal and typeahead come from the headless primitive, not from us.

Focus ring (WCAG 2.2 SC 2.4.13)

Not focusable — no focus indicator required.

Reduced motion

No animation to gate.

ARIA in the source

None — semantics come from the element or the Base UI primitive rather than hand-written ARIA.

Examples

3 more states from the same story file.

R-rule compliance

Every primitive in @interlace/ui models to the portable 26-rule floor enforced by the componentApi ESLint preset. The cells below pin exactly where each rule applies in this file.

Dependencies

Base UI primitive

@base-ui/react/popover

Lucide icons

none

NPM dependencies

• @base-ui/react

Registry dependencies

• @interlace/theme
• @interlace/cn

Source

The full implementation — components/ui/popover.tsx once installed.

'use client';

import * as React from 'react';

// @interlace/popover v1.3.0 — Interlace design system.
// Docs, props and live preview: https://ds.interlace.tools/c/popover
// What changed since: https://ds.interlace.tools/c/popover#history
// Generated banner — keep it, the upgrade diff reads this version.

/**
 * @interlace/ui — Popover
 *
 * A non-modal floating panel anchored to its trigger. It dismisses on Escape
 * and on an outside click and returns focus to the trigger, but it does NOT
 * trap focus or make the page inert.
 *
 * That is the line between this and Dialog/Sheet, and it is the reason to pick
 * one over the other.
 *
 * Wraps @base-ui/react/popover: Base UI owns the open state, the dismissal and

…209 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.