> 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/button.md).

# ε Button

Element: A click/tap-able screen element used to build other elements and components, ie. Button Panel, ListItem with a right side button etc.

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

* Parent: [Button Panel](https://able.bucca.com/core/components/button-panel.md), [Button Bar](https://able.bucca.com/core/overview/button/button-bar.md), Multiple others
* Child: [Label](https://able.bucca.com/core/overview/label.md)

## Properties

**Style**: The visual appearance (styling) of the object

<div align="center"><figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FaXNnWl9ibBGLG33ioHgL%2FStyle.png?alt=media&amp;token=7f205f69-6531-43f7-8474-4a927f4eba48" alt=""><figcaption></figcaption></figure></div>

* Primary (default)
* Secondary
* Dark
* Neutral
* Light

**Type**: A way to structure high level variations of an object into like collections

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2Fd8t7ONtVGdnG6IeV9ZL3%2FType.png?alt=media&amp;token=336a7704-6956-44dc-b62c-8fbeaef2e4ac" alt=""><figcaption></figcaption></figure>

* Fill (default)
* Line
* Text

**Shape**: The different border treatments for the surface of the object

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2Fd60hm6HY1yNDqWhvv9j1%2FShape.png?alt=media&amp;token=0bed8077-e962-4484-98a6-89d25a6e44ad" alt=""><figcaption></figcaption></figure>

* Rounded (default)
* Square

**Size**: The general size of the object in relation to others

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FG0HLXR0PvB4EqGWRF8HW%2FSize.png?alt=media&amp;token=ece1a93e-f4fb-4b43-b859-37c3dbb3aa3a" alt=""><figcaption></figcaption></figure>

* XSmall
* Small
* Medium (default)
* Large
* Dynamic: The width AND height can be set to any value, this differs from the others which have FIXED heights.

**State**: The possible visual appearances, which are also tied to functionality of the given object. ie Disabled and the object can not be interacted with and visually shows that.

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FyThqOlvfJ9JIe6dFqZRt%2FState.png?alt=media&amp;token=e0fe0c5e-0bf3-4269-be9f-2e070f395c75" alt=""><figcaption></figcaption></figure>

* Enabled (default)
* Disabled
* Hover: Web/Desktop only
* Pressed
* Focus

## Usage

**Loading** - The ability to display a spinner on a button to represent action being taken to search or get information.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://able.bucca.com/core/overview/button.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
