A button that opens a dropdown menu with action items. The menu starts open for preview.
A button that opens a dropdown menu with action items. The menu starts open for preview.
A compound-mode menu whose rows are titled in groups. Each DropdownMenuGroup renders a role="group" named by its heading; arrow keys and typeahead skip the heading.
Dropdown menu with custom-rendered items using DropdownMenuItem for icons and descriptions.
Action menu with dividers separating safe and destructive operations. Use for row-level actions on items like documents, projects, or records.
Chooses a bottom sheet for compact touch surfaces and an anchored popover otherwise. The media query is product policy, while DropdownMenu owns both presentations.
Menu with selectively disabled items based on permissions. Use when some actions require higher privileges, like admin-only operations.
Overflow menu triggered by an icon-only button with no chevron or label text. Use for row-level actions in tables, cards, or lists where a text button would take too much space.
Menu items organized into titled sections for easy scanning. Use when you have 6+ actions that fall into distinct categories, like Create vs Manage.
Action menu with a nested submenu. Hover or Right arrow opens the flyout; Left arrow / Escape closes it. Use to group related destinations or secondary actions without crowding the top level.
Titled groups around a radio group and checkbox rows — the rows the data API cannot express, which is why the heading lives in compound mode.
Dropdown menu items with labels and secondary descriptions. Use DropdownMenuItem to render custom menu entries with consistent styling.
Compose a Layout with DrawerHeader, the fields in LayoutContent, and Cancel and Save in a pinned LayoutFooter. purpose="form" keeps Escape but ignores scrim clicks, so a stray click outside does not discard edits.
A no-results empty state with an icon, descriptive message, and a call-to-action button.
Full empty state with icon, message, and action buttons. Use when a search returns no results, a filter clears all items, or a list has been emptied. The buttons give the user a way forward: go back, clear filters, or try a different query.
Smaller empty state with reduced spacing for constrained areas. Use inside sidebar panels, card widgets, or notification drawers where a full-size empty state would overwhelm the layout.
Empty state wrapped in a Card for first-time setup or onboarding. Use when the user has not created any items yet, like a project list, team roster, or dashboard widget that will fill with data once they take action.
A form field wrapping a text input with a label, description, and validation status.
Fields with helper text below the label. Use descriptions to explain format requirements, constraints, or what happens with the data, like "At least 8 characters" or "We will send a confirmation link".
Required and optional field indicators side by side. Use isRequired on fields the user must fill in, and isOptional to clarify which fields can be skipped.
All three validation states: error, warning, and success. Use error for invalid input, warning for potential issues like reserved names, and success to confirm valid entries like API keys.
Standalone field labels demonstrating required, optional, tooltip, and icon variations.
Field status messages in error, warning, and success states with attached and detached variants.
Standalone labels with required and optional indicators and a helper description. Use when labeling a custom control that does not render its own label.
Detached error and success messages for validation feedback. Use below checkboxes, switches, or custom controls where an attached status would overlap.
Showing 193–216 of 682