> 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/components/sheet/sheet-drag.md).

# Sheet Drag

Element: The area at the top or bottom of a sheet that the user can drag the size of the sheet larger or smaller.

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

* Parent: [Sheet](/core/components/sheet.md)
* Child: None

## Properties

### Location

* **Top:** The sheet drag is positioned at the top of the sheet, for use in the Bottom version of Sheet.
* **Bottom:** The sheet drag positioned at the bottom of the sheet, for use in the Top version of Sheet.

## Use

The entire surface of the Sheet Drag is a hit area to allow a tap/click and drag to change the height of the sheet to its other breakpoint (anchored) heights, as determined by the contents of the sheet. On a tap+drag the sheet gradually grows/shrinks and once released will snap to the closest breakpoint (anchor). For an example of in app use please see the Google/Apple Maps search sheet.


---

# 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/components/sheet/sheet-drag.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.