Context Menu

Displays a brief heading and subheading to communicate any additional information or context a user needs to continue.

Default

Right click here

Disabled items

Right click here

Link items

Right click here

Prefix and suffix

Right click here
Right click here

Best Practices

When to use

  • Use ContextMenu for power-user shortcuts on right-click or long-press over a row, file, or canvas object.
  • ContextMenu must never be the only entry point for an action. Mirror every item in a visible Menu trigger or row button so mouse-only and keyboard-only users have parity.
  • For a global command palette, use CommandMenu; for a dropdown opened from a visible trigger, use Menu.

Behavior

  • Bind to right-click on desktop and long-press on touch. Suppress the native browser menu only on the trigger area, not the whole page.
  • Position the menu at the pointer; if it would overflow the viewport, flip horizontally then vertically before clipping.
  • Close on activation, Escape, and outside-click. Don’t close on hover-out.

Content

  • Items follow the same rules as Menu: Title Case Verb + Noun (Open in New Tab, Copy URL, Delete Deployment). Bare verbs are wrong.
  • End with only when activating opens a follow-up dialog (Rename…, Move to Folder…).
  • Group destructive items at the bottom with a divider and keep the destructive label Verb + Noun. Delete alone never ships.

Accessibility

  • Trigger the keyboard menu key (Shift+F10 on Windows/Linux, the menu key, or platform equivalent) to open the same menu without right-click.
  • Up/Down arrows move focus, Enter/Space activates, Escape closes and returns focus to the row.
  • Don’t bury destructive items behind nested submenus. One level deep keeps keyboard navigation predictable.