RhombusKit

Menu

A menu presents a list of actions on a surface that opens from a trigger you project. RhombusKit wraps Material's <mat-menu> with the token contract and a declarative items API — each MenuItem carries its own action callback, so dispatch is co-located with the item.

Example

When to use

  • Use a menu to collect secondary or overflow actions behind one trigger (row actions, a “more” button) rather than crowding them all onscreen.
  • When each entry is a single, fire-and-forget action — the homogeneous items list keeps dispatch co-located with each row.

When not to use

  • For rich, interactive panels — date grids, filter forms, multi-control pickers — use a Popover; a flat item list can't express them.
  • For the round icon-button trigger on a table row, reach for the Overflow Menu preset instead of wiring [iconButton]="true" by hand.
  • For a short, non-interactive hint, use a Tooltip.
  • For a task that must block the rest of the UI until resolved, use a Dialog.

Related components

  • Overflow Menu — the icon-button preset of this menu.
  • Popover — arbitrary interactive content off a trigger.
  • Tooltip — lightweight hover/focus hints.
  • Dialog — blocking modal surfaces.

Was this page helpful?