The most basic list group is an unordered list with list items and the proper classes. Build upon it with the options that follow, or with your own CSS as needed.
Add .active to a .list-group-item to indicate the current active selection.
Add .disabled to a .list-group-item to make it appear disabled. Note that some elements with .disabled will also require custom JavaScript to fully disable their click events (e.g., links).
Use < a>s or < button>s to create actionable list group items with hover, disabled, and active states by adding .list-group-item-action. We separate these pseudo-classes to ensure list groups made of non-interactive elements (like < li>s or < div>s) don’t provide a click or tap affordance.
Be sure to not use the standard .btn classes here.
With < button>s, you can also make use of the disabled attribute instead of the .disabled class. Sadly, < a>s don’t support the disabled attribute.
Add .list-group-flush to remove some borders and rounded corners to render list group items edge-to-edge in a parent container (e.g., cards).
Add the .list-group-numbered modifier class (and optionally use an < ol> element) to opt into numbered list group items. Numbers are generated via CSS (as opposed to a < ol>s default browser styling) for better placement inside list group items and to allow for better customization.
Numbers are generated by counter-reset on the < ol>, and then styled and placed with a ::before pseudo-element on the < li> with counter-increment and content.
These work great with custom content as well.
Add .list-group-horizontal to change the layout of list group items from vertical to horizontal across all breakpoints. Alternatively, choose a responsive variant .list-group-horizontal-{sm|md|lg|xl|xxl} to make a list group horizontal starting at that breakpoint’s min-width. Currently< b> horizontal list groups cannot be combined with flush list groups.
ProTip: Want equal-width list group items when horizontal? Add .flex-fill to each list group item.
Use contextual classes to style list items with a stateful background and color.
Contextual classes also work with .list-group-item-action for < a> and < button> elements. Note the addition of the hover styles here not present in the previous example. Also supported is the .active state; apply it to indicate an active selection on a contextual list group item.
Add badges to any list group item to show unread counts, activity, and more with the help of some utilities.
Add nearly any HTML within, even for linked list groups like the one below, with the help of flexbox utilities.
Place Bootstrap’s checkboxes and radios within list group items and customize as needed. You can use them without < label>s, but please remember to include an aria-label attribute and value for accessibility.
You can use .stretched-link on < label>s to make the whole list group item clickable.
As part of Bootstrap’s evolving CSS variables approach, list groups now use local CSS variables on .list-group for enhanced real-time customization. Values for the CSS variables are set via Sass, so Sass customization is still supported, too.
Used in combination with $theme-colors to generate the contextual variant classes for .list-group-items.
Loop that generates the modifier classes with an overriding of CSS variables.
Use the tab JavaScript plugin—include it individually or through the compiled bootstrap.js file—to extend our list group to create tabbable panes of local content.
You can activate a list group navigation without writing any JavaScript by simply specifying data-bs-toggle="list" or on an element. Use these data attributes on .list-group-item.
Enable tabbable list item via JavaScript (each list item needs to be activated individually):
You can activate individual list item in several ways:
To make tabs panel fade in, add .fade to each .tab-pane. The first tab pane must also have .show to make the initial content visible.
Activates your content as a tab element.
You can create a tab instance with the constructor, for example:
When showing a new tab, the events fire in the following order:
If no tab was already active, then the hide.bs.tab and hidden.bs.tab events will not be fired.