Overflow Menu
Overview
Usage
Examples
API
An overflow menu tucks a set of secondary actions behind a “···” icon-button trigger — the familiar pattern for per-row or per-card actions. <rhombus-overflow-menu> wraps <mat-menu> and is driven entirely by an items array, with the panel themed through the token contract.
Example
When to use
- Use an overflow menu to collapse secondary actions that would clutter a row or toolbar. Keep a view's primary action as a visible Button; only the supporting actions belong in the menu.
- Reach for it on dense surfaces — data-table rows, list items, cards — where space is tight and the actions are contextual to one entity.
When not to use
- For a text-triggered action list (not an icon button), use a Menu directly — overflow menu is just its icon-button preset.
- For rich, interactive panels (date grids, filter forms, multi-control pickers), use a Popover — a menu only expresses a flat list of actions.
- For a single, prominent action, use a Button rather than hiding it behind an overflow trigger.
Related components
- Menu — the text-triggered base this preset is built on.
- Data Table — the canonical home for per-row overflow actions.
- Popover — for interactive panels a menu can't express.
- Button — for primary actions that stay visible.
Was this page helpful?