A split button combines several related actions into a single control. The primary action is immediately accessible, while additional options are hidden in a dropdown menu.
A split button follows the same visual variants as a regular button.
The primary action can be labeled with a caption and illustrated with an icon. In the variant without a caption, the menu button becomes narrower.
Long text in the primary button does not wrap to a new line — it is truncated with an ellipsis. Avoid buttons with long text.
Either the primary or secondary action can be disabled individually, or the entire group can be disabled at once.
The Progress state can be combined with any other state (Normal, Disabled, Active). Like the Disabled state, it can be applied to the entire button group or to an individual element.
Menu positioning is configured the same way as in the Dropdown component. When the menu width is approximately equal to the split button's size, it is better to align them for visual consistency.
role="group": it ties the two actions together while each button stays a separate tab stop. When a page holds several split buttons, name the group — <kbq-split-button aria-label="Save document">.<button kbq-button aria-label="More options" [kbqDropdownTriggerFor]="menu">.aria-expanded, so assistive technology announces whether the menu is currently open.Tab reaches the primary button and then the trigger, Enter and Space activate the focused one. On the trigger ArrowDown also opens the menu, and Escape closes it and returns focus to the trigger — the same model as in Dropdown.disabled attribute on a <button> host, and through aria-disabled on hosts without native support, such as <a>.A split button is often confused with the more common button menu, which consists of a single element that opens a dropdown list of commands. Use a split button only in exceptional cases: