Dropdown

A dropdown is a flexible component that displays a list of actions or options to the user. It should not be confused with Select, which is used in forms as a way for the user to make a selection from a list.

Usage

When to use

• To display a list of actions or links under a single button toggle.
• To allow singular or multiple selection outside of a form, such as within filtering.
• To provide the user with a way to easily switch context within the application.

When not to use

• In forms when providing the user with options to choose from, consider Select.

Toggle

Types

Toggles come in two variant types: button and icon.

Size

ToggleButtons come in two sizes: small and medium. This allows for placement in ButtonSets with buttons of the same size.

ToggleIcons come in two sizes: small and medium.

Chevron usage

Open Toggles use icon chevron-up, while closed Toggles use chevron-down.

ToggleButtons require a visible chevron to indicate interactivity and provide distinction between Dropdowns and standard Buttons.

We strongly recommend providing visible chevrons on most instances of ToggleIcons to indicate interactivity. That said, it’s common to see ToggleIcons that use the more-horizontal icon without chevrons. Their placement, usually in the last column of a Table, is typically indicative of this type of interaction.

List

Placement

Lists can be positioned to the left or right of the Toggle, and above or below the Toggle to fit more appropriately within the UI. Lists do not currently have collision detection.

Size

Width

By default, Lists have a minimum width of 200px and a maximum width of 400px. This means if there’s a long string in a ListItem, the List will automatically expand up to 400px to accommodate the content before it wraps.

If you do not want the width of the List to expand automatically to accommodate the widest ListItem, you can indicate a specific width between 200px–400px.

Height

The height of the ListContainer is automatically determined based on the contents, but the height can also be set manually. We recommend setting the height manually if you know the list will be long. In code, the @height property actually acts as a max-height.

Header

A Header provides a fixed space at the top of the List. Typically, Headers house a search feature that allows the user to search/filter through the available options in the list. This is great for really long lists when filtering on complex datasets.

Footer

A Footer provides a fixed space at the bottom of the List. Typically, Footers house actions related to the ListItems, e.g., when found in a filtering pattern an "Apply" Button can be used to submit the selections.

ListItem

Types

For maximum flexibility, we offer a variety of ListItems options.

Interactive ListItems

Use Interactive ListItems for actions (buttons) or links.

• Use Interactive - Critical for destructive actions.
• Use Interactive - Action for everything else.

Selection ListItems

Selection ListItems allow the user to select one or more options within a Dropdown.

• Use Checkmark for switching context, e.g., organization switchers, project switchers, etc. Use for single selection only, as it doesn't provide enough indication that multi-selection is possible. For multi-selection, use Checkbox.
• Use Checkbox for multi-selection within a form or larger filter pattern.
• Use Radio for single selection within a form or larger filter pattern.

Non-interactive

Non-interactive ListItems help provide structure and context to a Dropdown. Types include: Description, Loading, Separator, and Title.

Generic

The Generic ListItem allows you to add custom content in place of a ListItem. It includes predefined left and right padding to ensure proper alignment with other ListItems in the List.

Icon usage

Icons in ListItems are optional. Generally, we recommend letting the text speak for itself, but icons can add value in the following situations:

• When they reinforce the content, e.g., edit for an edit or rename action.
• When using Critical ListItems; read more about how color blind users see critical actions in our UIs.
• To avoid inconsistent icon use within the same List. Instead use icons in all ListItems. Doing so keeps the text aligned so the eye can scan the list of options more easily.

Content

While there are no character limits for ListItems, we recommend keeping them short and concise so the List is easy to scan.

Critical action patterns

We recommend adding a second confirmation layer after the user clicks “Delete” (e.g., showing a confirmation Modal that requires the user to take another action before proceeding). This safeguards against accidental clicks by requiring users to confirm the destructive action.

How to use this component

To make the invocation more flexible and intuitive, we provide contextual components for Toggles, ListItems, Header and Footer. For example, <Hds::Dropdown::ListItem::Separator /> would be contextually expressed as <dd.Separator />.

<Hds::Dropdown as |dd|>
  <dd.ToggleButton @text="Menu" />
  <dd.Title @text="Title Text" />
  <dd.Description @text="Descriptive text goes here." />
  <dd.Interactive @href="#" @text="Add" />
  <dd.Interactive @href="#" @text="Add More" />
  <dd.Interactive @href="#" @text="Add Another Thing Too" />
  <dd.Separator />
  <dd.Interactive @route="components" @icon="trash" @text="Delete" @color="critical" />
</Hds::Dropdown>

ToggleButton

The basic invocation of ToggleButton requires @text to be passed. By default, it renders a primary button with a chevron icon.

<Hds::Dropdown as |dd|>
  <dd.ToggleButton @text="Text Toggle" />
  <dd.Interactive @route="components" @text="Item One" />
  <dd.Interactive @route="components" @text="Item Two" />
  <dd.Interactive @route="components" @text="Item Three" />
  <dd.Interactive @text="Item Four (closes on click)" {{on "click" dd.close}} />
  <dd.Separator />
  <dd.Interactive @route="components" @text="Delete" @color="critical" @icon="trash" />
</Hds::Dropdown>

Alternatively, pass secondary to @color to display a secondary button with a chevron icon.

<Hds::Dropdown as |dd|>
  <dd.ToggleButton @text="Text Toggle" @color="secondary" />
  <dd.Interactive @route="components" @text="Item One" />
  <dd.Interactive @route="components" @text="Item Two" />
  <dd.Interactive @route="components" @text="Item Three" />
  <dd.Interactive @text="Item Four (closes on click)" {{on "click" dd.close}} />
  <dd.Separator />
  <dd.Interactive @route="components" @text="Delete" @color="critical" @icon="trash" />
</Hds::Dropdown>

ToggleIcon

ToggleIcon as overflow menu

Overflow menus are often found in the last column of a Tables. This is the only use case where it is acceptable to use @hasChevron=false. @text is still required, because it supplies the aria-label for ToggleIcon.

<Hds::Dropdown as |dd|>
  <dd.ToggleIcon @icon="more-horizontal" @text="Overflow Options" @hasChevron={{false}} />
  <dd.Interactive @route="components" @text="Create" />
  <dd.Interactive @route="components" @text="Read" />
  <dd.Interactive @route="components" @text="Update" />
  <dd.Separator />
  <dd.Interactive @route="components" @text="Delete" @color="critical" @icon="trash" />
</Hds::Dropdown>

ToggleIcon as user menu

@text is still required, because it supplies the aria-label for ToggleIcon.

<Hds::Dropdown as |dd|>
  <dd.ToggleIcon @icon="user" @text="user menu" />
  <dd.Title @text="Signed In" />
  <dd.Description @text="email@domain.com" />
  <dd.Separator />
  <dd.Interactive @route="components" @text="Settings and Preferences" />
  <dd.Interactive @route="components" @text="Delete" @color="critical" @icon="trash" />
</Hds::Dropdown>

ToggleIcon with other icons

Pass any icon name to @icon to change the icon used in ToggleIcon. @text is still required, because it supplies the aria-label for ToggleIcon.

<Hds::Dropdown as |dd|>
  <dd.ToggleIcon @icon="settings" @text="settings menu" />
  <dd.Title @text="Signed In" />
  <dd.Description @text="email@domain.com" />
  <dd.Separator />
  <dd.Interactive @route="components" @text="Settings and Preferences" />
  <dd.Interactive @route="components" @text="Delete" @color="critical" @icon="trash" />
</Hds::Dropdown>

List placement

By default, the list is positioned below the button, aligned to the right. To change the list position pass bottom-left, top-left, or top-right to @listPosition on the Dropdown component.

<Hds::Dropdown @listPosition="bottom-left" as |dd|>
  <dd.ToggleButton @text="Text Toggle" />
  <dd.Interactive @route="components" @text="Item One" />
  <dd.Interactive @route="components" @text="Item Two" />
  <dd.Interactive @route="components" @text="Item Three" />
  <dd.Interactive @text="Item Four (closes on click)" {{on "click" dd.close}} />
  <dd.Separator />
  <dd.Interactive @route="components" @text="Delete" @color="critical" @icon="trash" />
</Hds::Dropdown>

In contexts where the Dropdown needs to be inline, to inherit the alignment from a parent, you can use the @isInline argument (and set the @listPosition accordingly to your needs):

<div class="doc-dropdown-mock-text-align-right">
  <Hds::Dropdown @isInline={{true}} @listPosition="bottom-right" as |dd|>
    <dd.ToggleButton @text="Text Toggle" @color="secondary" />
    <dd.Interactive @route="components" @text="Item One" />
    <dd.Interactive @route="components" @text="Item Two" />
    <dd.Interactive @route="components" @text="Item Three" />
  </Hds::Dropdown>
</div>

List size

You can explicitly control the height or width of a list. Any acceptable value (px, rem, em) can be declared:

<Hds::Dropdown @isInline={{true}} @height="170px" @width="250px" as |dd|>
  <dd.ToggleButton @text="Text Toggle" />
  <dd.Interactive @route="components" @text="Item One" />
  <dd.Interactive @route="components" @text="Item Two" />
  <dd.Interactive @route="components" @text="Item Three" />
  <dd.Interactive @route="components" @text="Item Four" />
  <dd.Interactive @route="components" @text="Item Five" />
  <dd.Interactive @route="components" @text="Item Six" />
  <dd.Interactive @route="components" @text="Item Seven" />
</Hds::Dropdown>

List footer

It is possible that you may want to add a list footer for things like a set of buttons for a filter control:

<Hds::Dropdown @height="284px" as |dd|>
  <dd.ToggleButton @icon="tag" @text="Tags" @color="secondary" />
  <dd.Checkbox>access</dd.Checkbox>
  <dd.Checkbox>homework</dd.Checkbox>
  <dd.Checkbox>discovery</dd.Checkbox>
  <dd.Checkbox>memories</dd.Checkbox>
  <dd.Checkbox>music</dd.Checkbox>
  <dd.Checkbox>pharell</dd.Checkbox>
  <dd.Checkbox>punk</dd.Checkbox>
  <dd.Checkbox>random</dd.Checkbox>
  <dd.Checkbox>robots</dd.Checkbox>
  <dd.Checkbox>tag</dd.Checkbox>
  <dd.Footer @hasDivider={{true}}>
    <Hds::ButtonSet>
      <Hds::Button @text="Apply filters" @isFullWidth={{true}} @size="small" />
      <Hds::Button @text="Cancel" @color="secondary" @size="small" />
    </Hds::ButtonSet>
  </dd.Footer>
</Hds::Dropdown>

ListItem::Interactive

ListItem::Interactive renders the correct element based on the passing of a @route, @href, or the addition of a click event (e.g., {{on "click" this.myAction}}). Internally, the component uses the Hds::Interactive utility component.

Rendering a button

If you add an event handler (no @href or @route), a <button> element will be rendered:

{{!-- The Doc::ListContainer component is just to help the component render properly --}}
<Doc::ListContainer class="hds-dropdown__list">
  <Hds::Dropdown::ListItem::Interactive {{on "click" this.myAction}} @text="Run command" />
</Doc::ListContainer>

Rendering a link with @href

If you pass an @href argument, a link (<a> element) will be generated:

{{!-- The Doc::ListContainer component is just to help the component render properly --}}
<Doc::ListContainer class="hds-dropdown__list">
  <Hds::Dropdown::ListItem::Interactive @href="https://www.hashicorp.com/request-demo/terraform" @text="Request a demo" />
</Doc::ListContainer>

Rendering a LinkTo (with @route)

Pass a @route to render Ember <LinkTo>. If the route is external to your current engine, pass @isRouteExternal=true to use <LinkToExternal> instead of <LinkTo>. For more details see the Hds::Interactive component documentation. All the standard arguments for the <LinkTo/LinkToExternal> components are supported (e.g., models/model/query/current-when/replace).

{{!-- The Doc::ListContainer component is just to help the component render properly --}}
<Doc::ListContainer class="hds-dropdown__list">
  <Hds::Dropdown::ListItem::Interactive @route="my.page.route" @model="my.page.model" @text="Activate cluster" />
</Doc::ListContainer>

With a loading “interactive” item

There may be use cases when it’s necessary to put an item in a “loading” state while the app performs some operations (e.g., asynchronously checking the user’s permissions to execute a certain operation once the Toggle’s been clicked).

Pass the argument @isLoading=true to the item. This will show a “loading” icon (even if an argument @icon is provided) and sets the item as non-interactive until the value of @isLoading is set to false again.

<Hds::Dropdown as |dd|>
  <dd.ToggleIcon @icon="more-horizontal" @text="Overflow Options" @hasChevron={{false}} />
  <dd.Interactive @route="components" @isLoading={{true}} @text="Edit cluster" @color="action" @icon="edit" />
  <dd.Interactive @route="components" @text="Delete" @color="critical" @icon="trash" />
</Hds::Dropdown>

ListItem::CopyItem

To enable users to copy a snippet of code (eg. URLs, secrets, code blocks, etc.).

Using the @isTruncated argument it is possible to constrain the text to one-line and truncate it if it does not fit the available space. Care should be taken in choosing to use this feature as there are accessibility concerns.

<Hds::Dropdown as |dd|>
  <dd.ToggleButton @listPosition="bottom-left" @text="Create run task" @color="secondary" />
  <dd.Title @text="Integrate with Terraform Cloud" />
  <dd.Description @text="Create a new run task in Terraform using the URL and key below." />
  <dd.CopyItem @text="https://api.cloud.hashicorp.com" @copyItemTitle="Endpoint URL" />
  <dd.CopyItem @isTruncated={{true}} @text="91ee1e8ef65b337f0e70d793f456c71d91ee1e8ef65b337f0e70d793f456c71d" @copyItemTitle="HMAC Key" />
</Hds::Dropdown>

ListItem::Checkmark

For switching context (e.g., organization switchers, project switchers, etc.) use ListItem::Checkmark.

<Hds::Dropdown @listPosition="bottom-left" as |dd|>
  <dd.ToggleButton @text="HCP Design Sandbox" @color="secondary" />
  <dd.Checkmark>ACME Org</dd.Checkmark>
  <dd.Checkmark @selected={{true}}>HCP Design Sandbox</dd.Checkmark>
  <dd.Footer @hasDivider={{true}}>
    <Hds::Link::Standalone @icon="list" @text="All Organizations" @color="secondary" @href="#" />
  </dd.Footer>
</Hds::Dropdown>

ListItem::Checkbox

For multi-selection within a form or larger filter pattern use ListItem::Checkbox.

<Hds::Dropdown @listPosition="bottom-left" as |dd|>
  <dd.ToggleButton @count="2" @text="Status" @color="secondary" />
  <dd.Checkbox @count="4">Failing</dd.Checkbox>
  <dd.Checkbox @count="2" checked>Active</dd.Checkbox>
  <dd.Checkbox @count="1">Starting</dd.Checkbox>
  <dd.Checkbox @count="3" checked>Pending</dd.Checkbox>
  <dd.Footer @hasDivider={{true}}>
    <Hds::Button @text="Apply filters" @isFullWidth={{true}} @size="small" />
  </dd.Footer>
</Hds::Dropdown>

ListItem::Radio

For single selection within a form or larger filter pattern use ListItem::Radio.

<Hds::Dropdown @listPosition="bottom-left" as |dd|>
  <dd.ToggleButton @text="Status" @color="secondary" />
  <dd.Radio name="status" @count="4">Failing</dd.Radio>
  <dd.Radio name="status" @count="2" checked>Active</dd.Radio>
  <dd.Radio name="status" @count="1">Starting</dd.Radio>
  <dd.Radio name="status" @count="3">Pending</dd.Radio>
  <dd.Footer @hasDivider={{true}}>
    <Hds::Button @text="Apply filters" @isFullWidth={{true}} @size="small" />
  </dd.Footer>
</Hds::Dropdown>

ListItem::Generic

ListItem::Generic allows you to pass custom elements to the Dropdown.

<Hds::Dropdown @listPosition="bottom-left" as |dd|>
  <dd.ToggleButton @text="Text Toggle" @color="secondary" />
  <dd.Title @text="Integrate with Terraform Cloud" />
  <dd.Description @text="Create a new run task in Terraform using the URL and key below." />
  <dd.Generic>
    <Hds::Link::Standalone @text="Watch tutorial video" @icon="film" @href="/" />
  </dd.Generic>
</Hds::Dropdown>

Component API

The Dropdown component is composed of different child components each with their own APIs:

• The Dropdown component
  • Optional header and footer
• Toggle components to open/close the Dropdown
  • ToggleButton
  • ToggleIcon
• ListItem components, to build the Dropdown’s list items
  • Description
  • Generic
  • Interactive
  • Separator
  • Title

Dropdown

Dropdown::Header and Dropdown::Footer

If the Dropdown content exceeds the height of the container, the header and footer remain fixed while the list of items adjusts its height.

Toggle::Button

Toggle::Icon

ListItem::Interactive

ListItem::Title

ListItem::Description

ListItem::Separator

ListItem::CopyItem

ListItem::Checkmark

ListItem::Checkbox

ListItem::Radio

ListItem::Generic

Anatomy

Dropdown

Toggle

ListItem

States

Toggle

ListItem

Interactive

Checkbox

Checkmark

Radio

Conformance Rating

This component is conditionally conformant.

1. When truncation occurs, a keyboard-only user cannot access the truncated content.
2. The component is no longer conformant if the chevron icon is removed from the ToggleButton.

Known issues

ToggleIcon with no chevron

Setting @hasChevron to false on ToggleIcons doesn’t provide enough affordance; it’s not quickly seen as actionable.

Color blind users and critical actions

Color blind users, specifically those with Achromatopsia, may have a hard time perceiving Critical ListItems within our Dropdown component.

To provide a more accessible experience, we recommend:

• Using strong, clear language for the text (e.g., “Delete…”, “Revoke…”, etc.).
• Adding a relevant icon that indicates the action is destructive (e.g., trash).
• Moving the Critical ListItem to the bottom of the list or the section.
  • If at the bottom of a list, consider adding a separator above the Critical ListItem to help separate it from other ListItems.
• Adding a second confirmation layer after the user clicks “Delete” (e.g., showing a confirmation Modal that requires the user to type “Delete” into a field before proceeding).

Keyboard navigation

Applicable WCAG Success Criteria

This section is for reference only. This component intends to conform to the following WCAG Success Criteria:

Support

If any accessibility issues have been found within this component, let us know by submitting an issue.