Context Menus

A context menu is a panel of actions that belongs to the object you opened it on (a table row, a chat message, a node on a canvas) and appears where that object is rather than in the page chrome. Everything in it acts on that one thing, which is what lets the labels stay short: the subject is already established by where the menu opened. Separators group the items by consequence, and the destructive one sits alone at the bottom.

The part that catches teams out is discovery. A right-click is invisible, a long-press is invisible and slow, and neither exists for someone driving the app from the keyboard. So a context menu should hold a second copy of actions that live somewhere else too, not the only copy. Where a row carries an action people need often, give the row a visible trigger that opens the same menu, and let the items print their shortcut hints, so the menu teaches the faster route it is standing in for.

9 blocks

Add elements

Flow builders, node pickers, command panels: the plus under a flow opens one picker beside it

Add elements, lands in place

Flow builders where you want to see where a node goes before you add it

Add elements, drill-in

Node pickers that must work the same on a phone: one card that goes deeper instead of wider

Profile menu

User rows, team directories, avatar-triggered actions: every action on a person, from a right-click on their row

Profile menu, identity card

Account menus, status and presence, anything that says who you are before it lets you act

Profile menu, row unfolds

Team directories and member lists where a row opens into its own actions instead of a popup

Message menu

Chat threads, comment reactions, inline message actions: every action on a message, from a click or right-click on its bubble

Message menu, tapback

Chat threads where a reaction is one tap and the actions stay out of the way

Message menu, next step in place

Chat threads where a follow-up question (a reply, a report) belongs in the menu itself instead of a new surface

01

Using Context Menus

Reach for it when

  • A table or directory row needs per-record actions that would crowd the row if drawn inline
  • A canvas or flow builder where a click should offer what can be added at that point
  • A chat message needs reactions and replies without a permanent toolbar on every bubble
  • A destructive action needs to sit apart from the ordinary ones, below a separator

Reach for something else when

  • The action is the main thing to do on the screen: put a button on the page, where a gesture nobody was told about cannot hide it
  • You are choosing a value rather than firing an action: a dropdown reports the choice back to the control that opened it
  • The panel would need its own search across hundreds of entries. That is a command menu, which is built to be typed at
02

Where it shows up

01

Record row actions

A directory or file list gives every row the same set of operations. Opening them from the row keeps the table clear of buttons, and the menu's subject is whichever row was clicked, so labels can stay one word long.

02

Canvas node pickers

A flow builder opens a panel of what can be added at this point, with a search field, tabs across categories and a submenu for nested types. The menu is the palette here, so it earns a footer of suggestions.

03

Message actions

A chat bubble opens a row of reactions and the actions belonging to that message (reply, copy, report) each printing its keyboard shortcut, so the menu teaches the faster path while it does the slower one.

04

Team member rows

An avatar row in a team directory opens status, move, edit and share, with delete kept below a separator, far from the item above it and drawn so it does not read as a peer.

03

Questions

What is the difference between a context menu and a dropdown menu?

A context menu is opened by acting on an object (a right-click, a long-press, or a trailing button on a row) and every item in it acts on that object. A dropdown hangs off a control that is always visible, and it usually reports a chosen value back to that control. Context menus act; dropdowns mostly select.

How do you make a context menu work on touch and with a keyboard?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.