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

# ε FAB

Element: The Floating Action Button with set sizes for display with or without a status badge.

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

* Parent: [App Bar - Bottom](https://able.bucca.com/core/components/app-bar.md)
* Child: [FABShape](https://able.bucca.com/core/overview/fab/fab-shape.md), [Badge](https://able.bucca.com/core/overview/badge.md)

## Properties

### Size

To account for multiple usecases the design system has established a set sizing standard for FAB's. The size and shape of the FAB is set in the base level feeder of FAB - Shape and passed to this level.

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FQxU1hCDOGf3w6J7vfL12%2FSize.png?alt=media&amp;token=60b374f7-3b6d-45f4-819b-b69844d64d0b" alt=""><figcaption></figcaption></figure>

* Tiny
* XSmall
* Small
* Medium
* Medium Extended

### Badge

Most of the time a FAB displays an icon as a metaphor for the primary action to take on the screens subject matter, but it does have the ability to carry a badge as well. For example, there may be a situation where the FAB acts as a shopping cart where the alert can serve as a cart count.

At the smaller sizes (Tiny, xSmall) of FAB the Badge only acts as a colored badge, meaning there is no numeric value or icon possible within the Badge. At the other sizes the numeric and icon badges are possible.

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FCIN81cjC8GRhKINsPg11%2FBadge.png?alt=media&amp;token=d3b9dc5f-a78d-442c-bb74-247b2190d38b" alt=""><figcaption></figcaption></figure>

### State

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FkFjwtCJqJAUmesT3EY2L%2FState.png?alt=media&amp;token=57ef15fe-361d-461a-b697-2e3a85965b67" alt=""><figcaption></figcaption></figure>

* Enabled
* Disabled
* Hover
* Pressed
* Focus

### Style

The color of the FAB can be set to the following color display options...

<figure><img src="https://217329376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MXJWCEk7b7vvAFeWpr2%2Fuploads%2FMBHg5FJZ9grQnY5ykend%2FStyle.png?alt=media&amp;token=203dfcf9-872d-4621-bc37-33cc6280c408" alt=""><figcaption></figcaption></figure>

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


---

# 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/fab.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.
