> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/bug-reports/capturing-a-bug-report/screenshot/screenshot-hover-state.md).

# Screenshot hover state

Capture tooltips, menus, and other hover-only UI using Screendesk’s capture delay.

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

{% stepper %}
{% step %}

### Open capture options

Open the Screendesk browser extension.

Click the chevron next to **Capture screenshot** to see more options.
{% endstep %}

{% step %}

### Pick a delay

Select a **3-second** or **6-second** delay.
{% endstep %}

{% step %}

### Start the capture

* For a cropped screenshot, click and drag to select an area.
* For a full screenshot, click once on the page.

When you release the mouse, the countdown starts.
{% endstep %}

{% step %}

### Set the hover state

During the countdown, hover the element you want to capture.

Keep the cursor in place until the timer ends.
{% endstep %}

{% step %}

### Annotate and share

After capture, add annotations if needed.

Select **Create** to generate a shareable link with the screenshot and diagnostics.
{% endstep %}
{% endstepper %}


---

# 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://docs.screendesk.io/bug-reports/capturing-a-bug-report/screenshot/screenshot-hover-state.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.