Popover
Keep a small set of preferences close to the control.
use blinc_cn as cn;
use blinc_core::reactive::Signal;
use blinc_layout::prelude::*;
pub fn popover_demo(confirmed: Signal<bool>) -> Div {
let notifications = confirmed;
div().class("demo-stack").class("demo-stack--center").child(
cn::popover(|_| div().child(cn::button("Preferences").variant(cn::ButtonVariant::Outline))).content(
move || {
div()
.class("demo-popover-form")
.child(cn::label("Notifications"))
.child(cn::switch(notifications).label("Email updates"))
},
),
)
}
@layer components {
.cn-popover-content {
font-family: var(--font-sans);
}
.cn-popover-content {
background: var(--surface-elevated);
border: 1px solid var(--border);
border-radius: var(--radius-md);
color: var(--text-primary);
box-shadow: var(--shadow-md);
padding: var(--space-4);
animation: cn-popover-enter var(--duration-normal) var(--ease-spring);
transform-origin: top center;
}
@keyframes cn-popover-enter {
from {
opacity: 0;
transform: scale(0.96) translateY(-4px);
}
to {
opacity: 1;
transform: scale(1) translateY(0);
}
}
}
Usage and properties
Keep a small set of preferences close to the control. 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 |
|---|---|---|---|
trigger / content | child builders | Construction | Preferences and notifications |
Keyboard and interaction
Tab stays inside the open popover and Escape or an outside click closes it. Focus returns to the trigger.
Customizing it
Add application CSS after the default component layer. These selectors are the restyling surface for this component:
.cn-popover-content
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 popover opens on click. Its trigger builder receives the current open value; the component manages toggling and dismissal:
let notifications = ctx.use_signal(true);
popover(|_open| div().child(button("Preferences")))
.content(move || {
div().flex_col().gap(3.0)
.child(text("Notifications"))
.child(switch(notifications).label("Email notifications"))
})
.side(PopoverSide::Bottom)
.align(PopoverAlign::Start)
.offset(8.0)
The content builder returns a Div. Runtime values inside it bind to
Signals; there is no public .open(signal) or .on_open_change(...) builder.
.class(..) targets the trigger wrapper. The separately mounted panel is
.cn-popover-content, so use that class to restyle the panel rather than a
descendant selector rooted at the trigger.
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.