Tooltip.
A little context, at the right moment.
The trigger needs its own accessible name. Installed Base UI tooltips are visual hints; essential instructions belong in persistent text. Keep popup content non-interactive, and use Popover for actions.
Make it yours
Preparing the example…
Composition
AnatomyThe trigger needs its own accessible name. Installed Base UI tooltips are visual hints; essential instructions belong in persistent text. Keep popup content non-interactive, and use Popover for actions.
Tooltip.Provider (delay)
└── Tooltip.Root
├── Tooltip.Trigger render=Button
└── Tooltip.Portal → Tooltip.Positioner → Tooltip.PopupA place to start
UsageImport the stylesheet once at your application root. This complete example reflects the properties selected above.
Loading example…
Details that make a difference
Examples & statesSizes
Compare the three Dixy shirt sizes side by side.
Loading source…
Visual treatments
Emphasis changes presentation while the primitive keeps behavior.
Loading source…
Corner radii
Contextual rounding applies to the control or surface; large panels stay readable.
Loading source…
Materials
Optional static finishes use the same public component. Import materials.css in your application.
Loading source…
The finer details
API referenceGenerated from Dixy’s local TypeScript interfaces. Native and Base UI Tooltip props are forwarded; this table covers the options Dixy adds.
TooltipPopup
| Prop | Type / description | Default |
|---|---|---|
size | "sm" | "md" | "lg"Component proportions; preserves the shared interaction target. | md |
variant | "soft" | "outline"Visual emphasis; behavioral state remains primitive-owned. | outline |
radius | "none" | "sm" | "md" | "lg" | "full"Contextual rounding; panels cap full rounding to preserve content. | Theme.radius |
material | "matte" | "glossy" | "soft" | "metal" | "paper"Optional static finish; import materials.css. | Theme.material |
Built from the same foundations
Styling tokensChange 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.
| Token | Purpose |
|---|---|
--dixy-popup-background | The component-specific starting point. |
--dixy-font-label-md | Control label font and line height; body roles remain readable in text inputs. |
--dixy-color-background-selected | Selected surfaces use semantic color across appearances. |
--dixy-color-border-focus | Focus indication remains visible independently of shadows. |
--dixy-spacing-inset-sm | Density-aware component padding. |
--dixy-motion-transition-feedback | Short state feedback, reduced by the inherited motion setting. |
Consider everyone
AccessibilityBase UI 1.9 tooltips are visual hints for sighted users. Give the trigger its own accessible name and repeat it in the hint. Essential instructions belong in persistent text, and interactive content belongs in Popover. Provide meaningful names and verify the complete interaction with a keyboard. Color alone must not communicate state.
Target: WCAG 2.2 AA. Automated tests cover selected behavior; manual screen-reader, contrast, and zoom validation remain part of the release checklist.
Build it. Then understand it.
Base UI 1.9 tooltips are visual hints for sighted users. Give the trigger its own accessible name and repeat it in the hint. Essential instructions belong in persistent text, and interactive content belongs in Popover. 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.
--dixy-popup-background