> For the complete documentation index, see [llms.txt](https://docs.bugbug.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbug.io/recording-tests-steps/recording-clicks.md).

# Recording clicks

How BugBug records clicks: every click, double click and right click is recorded automatically, together with changes in form elements such as checkboxes, radio buttons, selects and file uploads.

By default, when you record a test, BugBug records all your clicks. A double click and a right click are each recorded as their own action. You don't need to activate any recording mode.

When you move the mouse over an element, you see a thin purple border around it. It shows which element you're about to click.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FWGT8qU3XRjbagiFq7KZU%2Fimage.png?alt=media&amp;token=fd49763b-10f8-4f52-94e8-d6e1302078f9" alt=""><figcaption><p>Border around element pointed by mouse coursor</p></figcaption></figure>

## Form elements

Changes in form elements are also recorded automatically:

* checkboxes and radio buttons,
* options chosen in a select,
* date, time and color pickers,
* files chosen in a file input. A file can be up to 10 MB; a larger file is ignored and BugBug shows a message. Uploaded files are kept in [Files](https://docs.bugbug.io/organizing-tests/files.md).

## What isn't recorded as a click

* **Hover.** Moving the mouse over an element isn't recorded. See [Recording hover](https://docs.bugbug.io/recording-tests-steps/recording-hover.md).
* **Drag and drop.** See [Recording drag & drop](https://docs.bugbug.io/recording-tests-steps/recording-drag-and-drop.md).
* **Typing.** See [Recording keyboard typing](https://docs.bugbug.io/recording-tests-steps/recording-keyboard-typing.md).

You can change a recorded step to another action later. See [Actions](https://docs.bugbug.io/editing-tests/actions.md).


---

# 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://docs.bugbug.io/recording-tests-steps/recording-clicks.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.
