Dropdowns

A dropdown is a panel that hangs off a trigger, does one job and closes: a menu of actions, a list of values to pick from, or the account panel behind an avatar. The seven in this family cover that whole range, from a labelled form field that opens its list in place to a scrolling sheet of grouped actions.

Worth separating before you build one: a menu fires actions, a listbox holds values, and the two behave differently even though they look alike. A menu closes on the first click, because the click was the point. A multi-select panel must not, closing after every tick turns setting a handful of filters into a handful of round trips. Keyboard handling splits the same way, and so does what a screen reader announces. The other thing people miss is what should happen when a required field is opened and dismissed with nothing chosen: say so on the spot, rather than letting the submit be the first news of it.

14 blocks

Dropdown field

Forms: a labelled, required field that opens its list in a popover card

Command menu

Command palettes: type to filter, press to run, chords that run from anywhere

Pop-up list

Menus where each entry needs a line of explanation, shown only for the row you are on

Model picker

Choosing which models answer: Auto, or one or more

Model picker, compare

Choosing one model, or comparing up to three side by side

Model picker, search

Long model catalogues: filter, group by provider, hold the picks in the field

Take action

Long action sheets: grouped actions that run and confirm

Action menu, filter

Action menus long enough to need a search

Account menu

The avatar menu: settings, support, the plan with its usage and the way out

Account menu, upgrade

Account menus where the plan can be changed without leaving the menu

Account menu, drill-in

Short account menus whose details open as their own panes

Switch account

Multi-account apps: the accounts you can switch to, in rows

Switch account, flip

Switchers that show the swap: the picked mark flies into the header

Switch account, rail

Switchers with few accounts: every account a mark on a capsule

01

Using Dropdowns

Reach for it when

  • A form field whose answer comes from a known, short list
  • Actions that belong to one object and don't earn toolbar space
  • The avatar menu: settings, support, the plan, the way out
  • Filters where several options get set in one visit

Reach for something else when

  • More options than anyone will scroll: a combobox with type-ahead finds them faster
  • Two or three exclusive choices: radio buttons show them all without a click
  • The one action a screen exists for. That belongs on a visible button
02

Where it shows up

01

Account and plan menus

The avatar in the corner opens what is not navigation: profile and settings, support, the current plan with its upgrade path, and the sign-out that sits apart from everything above it.

02

Keyboard command menus

A short list of actions that each own a chord, opened from a search field. The chord printed on the row is how people graduate from clicking it to never opening the menu again.

03

Model pickers

Choosing among things that need explaining: a mark, a name, a badge and a line of description per row, with a checkbox on each when more than one can be on at a time.

04

Required form fields

A labelled field that opens its list underneath itself instead of floating over the form, keeping the header, the hint and the error footer where the reader is already looking.

03

Questions

Should a dropdown close after something is selected?

A menu of actions closes on the click, because the action was the point and leaving it open hides the result. A panel where several options can be on at once stays open, and closes on an outside click, on Escape, or on an explicit done control. A single-value picker closes on choice and puts focus back on its trigger.

What keyboard behaviour does a dropdown owe?

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.