NavigationComponentBeta

Menubar.

Familiar menus, working together.

Menubar coordinates keyboard movement between Menu roots. Each Menu keeps its own popup and item state. Use this desktop command pattern when menu semantics are appropriate, rather than replacing ordinary site links.

Make it yours

Preparing the example…

PROPERTIES4

Composition

Anatomy

Menubar coordinates keyboard movement between Menu roots. Each Menu keeps its own popup and item state. Use this desktop command pattern when menu semantics are appropriate, rather than replacing ordinary site links.

Component structure
Menubar
└── Menu.Root
    ├── Menu.Trigger
    └── Menu.Portal → Menu.Positioner → Menu.Popup → Menu.Item

A place to start

Usage

Import the stylesheet once at your application root. This complete example reflects the properties selected above.

Loading example…

Details that make a difference

Examples & states

Compare the three Dixy shirt sizes side by side.

Example loads as it comes into view.

Loading source…

Emphasis changes presentation while the primitive keeps behavior.

Example loads as it comes into view.

Loading source…

Contextual rounding applies to the control or surface; large panels stay readable.

Example loads as it comes into view.

Loading source…

The finer details

API reference

Generated from Dixy’s local TypeScript interfaces. Native and Base UI Menubar props are forwarded; this table covers the options Dixy adds.

Menubar

PropType / descriptionDefault
size"sm" | "md" | "lg"

Component proportions; preserves the shared interaction target.

md
variant"soft" | "outline" | "plain"

Visual emphasis; behavioral state remains primitive-owned.

plain
radius"none" | "sm" | "md" | "lg" | "full"

Contextual rounding; panels cap full rounding to preserve content.

Theme.radius
Explore the full Base UI API

Built from the same foundations

Styling tokens

Change Theme settings above to compare appearance, accent, neutral, radius, spacing density, motion and direction. Override component aliases on a Theme root so custom properties follow portaled content too. The wrapper merges className, style, refs and render composition with its owning primitive.

TokenPurpose
--dixy-primitive-gapThe component-specific starting point.
--dixy-font-label-mdControl label font and line height; body roles remain readable in text inputs.
--dixy-color-background-selectedSelected surfaces use semantic color across appearances.
--dixy-color-border-focusFocus indication remains visible independently of shadows.
--dixy-spacing-inset-smDensity-aware component padding.
--dixy-motion-transition-feedbackShort state feedback, reduced by the inherited motion setting.
Explore theme customization

Consider everyone

Accessibility

A menubar coordinates movement between Menu roots. Arrow keys move between menus and into their contents. Provide meaningful names and verify the complete interaction with a keyboard. Color alone must not communicate state.

Tab / Shift + TabMove through the available controls.
Arrow keys / SpaceUse the primitive’s directional or activation behavior where applicable.

Target: WCAG 2.2 AA. Automated tests cover selected behavior; manual screen-reader, contrast, and zoom validation remain part of the release checklist.

THE THINKING BEHIND IT

Build it. Then understand it.

A menubar coordinates movement between Menu roots. Arrow keys move between menus and into their contents. Component aliases reference Dixy semantic tokens; refs, events and render composition are forwarded unchanged. Visual settings follow Dixy shirt sizes, contextual radii and semantic tokens where applicable. Static finishes are optional, and reduced motion is immediate. Base UI keeps refs, state, events, keyboard and presence; this implementation pass does not establish WCAG conformance.

A token to follow--dixy-primitive-gap

Nothing up our sleeves

Source
UP NEXTMeter