> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/overview/toggle/toggle-bar.md).

# ε ToggleBar

Element: A collection of toggles with layout padding and behaviors. The bar component can have different background surfaces (colors) so we don't include a surface here.

[Styleguide Link](https://zpl.io/adyA535)

* Parent: [App Bar - Ext.](/core/components/app-bar/app-bar-ext.md), [Form > Toggle Button](/core/components/form/togglebutton.md)
* Child: [Toggle - Ctrl](/core/overview/toggle.md)

## Properties

### Layout Types

The options available in the "Toggle" element are capable here.

**Solo** - A grouping of solo toggles. An example of this could be different filters on a search, where each toggle is a different filter type (price, weight, rating, etc.)

**Group** (default)- When the toggle buttons are pushed together and are presented as a grouping of buttons. By default, this type exists as a singular choice (toggle on) from the group, but can function as a multi-select button as well. An example of this would be with a text editor grouping with bold, italic, underline where none or all of the groups options can be selected.

<figure><img src="/files/IQjjvTn6lieOePnzkN8b" alt=""><figcaption></figcaption></figure>

### Style

* Text (default)
* Icon

### Behavior

* **Fixed** (default)- New toggles that don't fit within the fixed width, wrap to the next row, growing the height of the bar - toggle.
* **Scroll** - Toggles that don't fit within the defined width of the parent container scroll off the side of the bar - toggle (screen).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://able.bucca.com/core/overview/toggle/toggle-bar.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.