Component

Overflow menu

Extra actions

may defer

This page is a reusable-component split from the source checklist row Overflow / split. The source row remains authoritative.

ContractOverflow / split
Job
Extra actions
Requirement
may defer
States / rules
Menu operable
Specified means
Job named if deferred
Hardest context
Editor overflow
Example

•••

Counter-example

Hidden actions with no overflow

Preview

Preview — not a published component API.

Duplicate
Archive
Delete

Usage

Job: Extra actions.

Job named if deferred

When not to use

Do not hide the primary action in overflow. Overflow is for secondary/local actions that cannot all remain visible.

Variants

The checklist row does not authorize this page to invent a final component API. Where the source rule names a variant, preserve it; otherwise keep the implemented variant set minimal and job-driven.

States & behavior

Menu operable

Universal interactive baseline

Default, Hover, Focus, Active/Pressed, and Disabled apply to interactive controls. Error, Loading, Empty, and Success apply where the component takes or reports data.

Accessibility

  • Use native semantics whenever they match the job.
  • Keep keyboard focus visible and distinct from hover.
  • Do not rely on color alone for state.
  • Maintain touch-operable targets and no hover-only actions.
  • For composite/overlay controls, document focus movement, Escape, and return focus as applicable.

Responsive behavior

Document sm/md/lg behavior explicitly: whether the component reflows, collapses, changes density, or stays structurally the same. Preserve touch targets and avoid hover-only behavior.

Theme comparison

The component job and interaction contract stay stable while product expression changes.

Base
Duplicate
Archive
Delete
Editorial
Duplicate
Archive
Delete
Native
Duplicate
Archive
Delete

Tokens

Bind the implementation to semantic roles for surface, text, border, focus, spacing, shape, and motion as needed. Actual token names must come from the implemented Foundation; this demo deliberately does not mint package-level token names.

Code / Storybook

No shared Building Blocks implementation is claimed here.

When this component exists in code, this section should link to its source and Storybook stories for executable states, Controls, viewport, accessibility checks, and interaction tests. The documentation page remains responsible for job, guidance, source contract, product decisions, themes, and Catalog lineage.