Dropdown Menu

A button-triggered command menu — items, checkbox and radio items, submenus, plus a `Compose` array shorthand. Wraps @base-ui/react/menu: Base UI owns open state, positioning, focus and typeahead; we own the popup and the rows.

overlayclient320pxuiv1.3.0

Preview

Dropdown Menu — live renderprimitives-dropdownmenu--default

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.

Via shadcn URL
npx shadcn@latest add https://ds.interlace.tools/r/dropdown-menu.json
With the @interlace alias
npx shadcn@latest add @interlace/dropdown-menu

Behavior

What this component does — the keyboard path, the measured colour, the text equivalent and the states it can be in. Every figure below is read out of the test or the source that enforces it by scripts/build-behavior-map.mjs, so nothing here can outlive the gate that keeps it true.

4 steps, 4 key presses — replayed on every PR by the play function of KeyboardFlow. Axe cannot press a key, so this — not the a11y scan — is what proves the component is operable without a mouse.

  1. 1The trigger advertises the menu it owns
  2. 2Enter opens the menu and focuses an itemEnterTab
  3. 3ArrowDown roves to the next itemArrowDown
  4. 4Escape closes and restores focus to the triggerEscape

Escape is locked, not merely exercised. This primitive is in KEYBOARD_DRIVEN + MUST_ASSERT_ESCAPE — deleting the dismissal assertion from the story fails overlay-nav-keyboard-lock, so the path above cannot quietly stop being tested.

Every semantic colour pair this component's own source uses, measured against the shipped hexes in all 4 theme × scheme combinations. The tightest is destructive on background at 7.60:1 (harbor · light), against a floor of 3:1.

Measured WCAG contrast ratios per token pair and theme
PairinterlacelightinterlacedarkharborlightharbordarkFloor
destructive on backgrounddestructive tint on the page surface8.31:110.43:17.60:110.03:13.0:1SC 1.4.11
muted-foreground on backgroundsecondary copy9.41:111.32:17.82:19.52:14.5:1SC 1.4.3
destructive on carddestructive tint inside a card8.31:19.66:18.02:19.09:13.0:1SC 1.4.11
muted-foreground on cardsecondary copy in a card9.41:110.48:18.25:18.64:14.5:1SC 1.4.3
accent-foreground on accenthover/highlight face8.98:110.46:18.95:19.65:14.5:1SC 1.4.3
popover-foreground on popovercopy in a popover19.65:115.71:118.72:114.69:14.5:1SC 1.4.3

Text pairs are held to 4.5:1 (WCAG 2.2 SC 1.4.3); borders, rings and chart axes to 3:1 (SC 1.4.11 non-text). Bold is the worst cell in the row — the one a brand fork has to keep an eye on.

Where it renders, how narrow it survives, and whether its lines are inside the coverage gate — three answers a consumer needs before the paste, not after the bug.

Render boundary
'use client'

Hydrates. It brings JavaScript to any route that imports it — put the boundary here, not at the page.

Minimum viewport
MIN_VIEWPORT = 320

Declared, not assumed. Below 320 CSS px the preflight contract draws a dev-mode outline — how to switch it on.

Coverage gate
not in the gate

The 100% gate currently covers src/charts/**/*.{ts,tsx} and src/lib/**/*.{ts,tsx} and src/primitives/{button-variants,data-state-model,meter-scale,skeleton-variants}.ts and src/primitives/{alert,aspect-ratio,avatar,badge,box,breadcrumb,button,callout,card,checkbox,code-editor,container,data-state,focus-ring,grade-badge,grid,input,label,meter,pagination,published-date,reading-time,section,section-boundary,separator,skip-link,stack,stat-strip,tag,textarea,typography,visually-hidden}.tsx and src/patterns/lint-playground.tsx. This file is outside it — the glob widens in phase 7.2.

History

This component is at v1.3.0, first shipped in @interlace/ui 1.0.0. The version is stamped as a banner into the file the install writes, so the copy in your tree says which one you have — compare it with the number above before deciding whether to re-run the install.

Import

17 named exports — pull the parts you need.

Public API
import { DropdownMenu, DropdownMenuCheckboxItem, DropdownMenuCompose, DropdownMenuContent, DropdownMenuGroup, DropdownMenuItem, DropdownMenuLabel, DropdownMenuPortal, DropdownMenuRadioGroup, DropdownMenuRadioItem, DropdownMenuSeparator, DropdownMenuShortcut, DropdownMenuSub, DropdownMenuSubContent, DropdownMenuSubTrigger, DropdownMenuTrigger, MIN_VIEWPORT } from '@/components/ui/dropdown-menu';

Anatomy

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

DropdownMenu                     (Menu.Root — renders no DOM node)
    ├─ DropdownMenuTrigger         (Menu.Trigger)
    └─ DropdownMenuContent         (Portal → Positioner(z-50) → Popup — data-min-viewport=320)
         ├─ DropdownMenuLabel      (a plain div — see below)
         ├─ DropdownMenuGroup      (Menu.Group)
         ├─ DropdownMenuItem       (Menu.Item — variant default | destructive)
         ├─ DropdownMenuCheckboxItem / DropdownMenuRadioGroup + RadioItem
         ├─ DropdownMenuSeparator  (a plain div with role="separator")
         ├─ DropdownMenuShortcut   (span, ml-auto)
         └─ DropdownMenuSub        (SubmenuRoot → SubTrigger + SubContent)
`DropdownMenuContent` is not a thin wrapper: it bundles Portal, Positioner
and Popup, so `side` / `align` / `sideOffset` are lifted onto it and any
other prop lands on the Popup.

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.

DropdownMenuComposeProps

PropTypeDescription
trigger*React.ReactNode
items*DropdownMenuComposeItem[]
openboolean
onOpenChange(open: boolean) => void
sideReact.ComponentProps<typeof DropdownMenuContent>['side']
alignReact.ComponentProps<typeof DropdownMenuContent>['align']
classNamestring

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/menu — 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
  • role="separator"

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.

RuleConceptWhere
R4Extends Base UI part props`React.ComponentProps<typeof BaseMenu.*>` on every wrapper
R6data-slot per partdropdown-menu / -trigger / -content / -item / -sub-… (15)
R7cn + ...rest`cn('…', className)` + `{...props}` on every styled part
R8Enum for item tone`variant = default
R10Composition seam`Compose` for the array case; the parts for everything else
R12Reuse over wrapBase UI owns open state, positioning, typeahead, roving focus
R14Declares min viewport`data-min-viewport` on the popup + exported const
R19Tokens only`bg-popover`, `bg-accent`, `text-destructive`, `ring-border`
R25Client componentRequired — Base UI Menu ships client hooks
R26Keyboard contractEscape-dismissal asserted by `DropdownMenu.stories.tsx`, locked by `overlay-nav-keyboard-lock`

Minimum viewport

This primitive declares MIN_VIEWPORT = 320 CSS px (DESIGN_PRINCIPLES #14). When mounted in a container narrower than this, the preflight contract draws a dev-mode outline so the regression is visible during local development.

Opt-in to the dev-mode warning
<body data-interlace-dev>...</body>

Add the data-interlace-dev attribute to the body in development builds only — preflight then outlines any primitive whose container is below its declared data-min-viewport.

Dependencies

Base UI primitive
@base-ui/react/menu
Lucide icons
  • CheckIcon
  • ChevronRightIcon
  • CircleIcon
NPM dependencies
  • @base-ui/react
  • lucide-react
Registry dependencies

Source

The full implementation — components/ui/dropdown-menu.tsx once installed.

444 lines · TypeScript
'use client';

import * as React from 'react';

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

/**
 * @interlace/ui — DropdownMenu
 *
 * A button-triggered command menu — items, checkbox and radio items, submenus,
 * plus a `Compose` array shorthand. Wraps @base-ui/react/menu: Base UI owns
 * open state, positioning, focus and typeahead; we own the popup and the rows.
 *
 * The menu ARIA is upstream's too, except where this file steps out of it on
 * purpose — see below.
 *
 * ## Anatomy

…424 more lines…

Registry JSON

The raw registry record — what the shadcn CLI fetches.