Menubar
Organise application commands in adjacent menus.

use blinc_cn as cn;
use blinc_core::reactive::{Signal, computed};
use blinc_layout::{binding::IntoReactive, prelude::*};
pub fn menubar_demo(choice: Signal<String>) -> Div {
div()
.class("demo-wide")
.child(
cn::menubar()
.menu("File", move |menu| {
menu.item("New project", move || choice.set("New project".into()))
.item("Save", move || choice.set("Saved".into()))
})
.menu("Edit", move |menu| {
menu.item("Undo", move || choice.set("Undo".into()))
.item("Redo", move || choice.set("Redo".into()))
}),
)
.child(
bound_text(computed(move |g| {
let choice = g.get(choice).unwrap_or_default();
if choice == "rust" {
"Choose an action".into()
} else {
choice
}
}))
.class("demo-caption"),
)
}
fn bound_text(value: impl IntoReactive<String>) -> Text {
Text::bound(value.into_reactive())
}
@layer components {
.cn-menubar,
.cn-menubar-trigger,
.cn-menubar-content,
.cn-menubar-item {
font-family: var(--font-sans);
}
.cn-menubar-trigger:focus-visible {
outline: 2px solid var(--focus-ring);
outline-offset: 2px;
}
.cn-menu-item {
color: var(--text-primary);
font-size: var(--text-sm);
cursor: pointer;
}
.cn-menu-item:hover:not(:disabled),
.cn-menu-item:focus-visible:not(:disabled) {
background: var(--accent-subtle);
}
.cn-menu-item:disabled {
opacity: 0.5;
cursor: not-allowed;
}
@keyframes cn-dropdown-menu-enter {
from {
opacity: 0;
transform: scale(0.96) translateY(-4px);
}
to {
opacity: 1;
transform: scale(1) translateY(0);
}
}
.cn-menubar {
background: var(--surface-elevated);
border: 1px solid var(--border);
border-radius: var(--radius-md);
padding: var(--space-1);
gap: var(--space-1);
}
.cn-menubar-trigger {
padding: var(--space-1-5) var(--space-3);
border-radius: var(--radius-sm);
cursor: pointer;
color: var(--text-primary);
font-size: var(--text-sm);
background: transparent;
}
.cn-menubar-trigger:hover {
background: var(--surface-elevated);
}
.cn-menubar-content {
animation: cn-dropdown-menu-enter var(--duration-fast) var(--ease-state);
transform-origin: top center;
}
.cn-menubar-content:has(.cn-menubar-item--has-submenu:hover) {
animation: none;
}
.cn-menubar-item {
padding: var(--space-2) var(--space-3);
}
}
Usage and properties
Organise application commands in adjacent menus. Apply CSS after the component layer to restyle the documented parts.
Use the installation guide to add blinc_cn and its component stylesheet. Create the fixture bindings once, and return the demo from your UI builder. Values marked Bound accept Signal/Computed sources where the API supports them; structural options configure the component at construction.
| Property | Type | Update model | This example |
|---|---|---|---|
menu | menu builder | Construction | File / Edit |
Keyboard and interaction
The menubar is one Tab stop. Left and Right, Home and End move between triggers; Down or Up opens the selected menu. Inside an open menu Left and Right switch to the adjacent menu, and submenus use Right to enter and Left to return.
Customizing it
Add application CSS after the default component layer. These selectors are the restyling surface for this component:
.cn-menubar.cn-menubar-trigger.cn-menubar-content.cn-menu-item.cn-menubar-item.cn-menubar-item--has-submenu
Theme and component variables: --primary, --text-primary, --text-secondary, --surface, --border, --radius-default, --duration-fast, --ease-state.
Built-in themes
The Live theme control installs Blinc's own theme bundles, including their colours, focus rings, corner shapes and motion tokens.
pub fn theme_bundle_for(name: &str) -> blinc_theme::ThemeBundle {
match name {
"restrained" => blinc_theme::RestrainedTheme::bundle(),
"expressive" => blinc_theme::ExpressiveTheme::bundle(),
_ => blinc_theme::HybridTheme::bundle(),
}
.with_css(blinc_cn::cn_styles::CN_STYLES)
}Download the default widget and component stylesheets. Sample assets and licenses are available in the asset guide.
Documentation
From the canonical component guide.
A menubar owns several menus. Each .menu(label, configure) receives a
MenubarMenu builder:
let action = ctx.use_signal(String::new());
menubar()
.menu("File", move |menu| {
menu.item("New", move || action.set("new".to_string()))
.item("Open", move || action.set("open".to_string()))
.separator()
.item_with_shortcut("Save", "Cmd+S", move || action.set("save".to_string()))
})
.menu("Edit", move |menu| {
menu.item("Undo", move || action.set("undo".to_string()))
.item("Redo", move || action.set("redo".to_string()))
})
A menubar is one Tab stop. Left/Right, Home/End move between its triggers; Down/Up opens the selected menu. Left/Right in an open root menu switches to the adjacent menu. Submenus use Right to enter and Left to return.
Restyle the shared .cn-menu-item:focus-visible highlight and
.cn-menubar-trigger:focus-visible outline. Menus also expose
.cn-context-menu, .cn-context-menu-item, .cn-dropdown-menu,
.cn-dropdown-item, .cn-menubar-content and .cn-menubar-item.
Platforms and version
The component API is available in Blinc 0.6.0. The Live example runs in a dedicated worker and requires a compatible GPU surface. Preview and Code remain available when Live cannot start. The canvas has a descriptive label; a full screen-reader DOM mirror is not provided. The gallery integration is based on revision e2e55c24e078.
Recordings and live demos use the default Hybrid theme with bundled Noto Sans. The recording uses a 560 × 320 logical viewport at twice that resolution. Live follows its container and actual display density. Source base revision · Exact build source · Artifact versions and checksums · Font license.