> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/studio/ui-elements/drop_down.md).

# drop\_down

A dropdown is a UI element that lets users select one value from a list. There are two types of dropdowns: list and menu.

List dropdowns are primarily used for selecting one value from a list of options. Menu dropdowns are primarily used for selecting one option from a list of values, where the user can type in their own choice.

## Automation

Usually when the UI element type is a dropdown, QATTS checks the tag name of the element is SELECT. If the tag name is not matched. it will throw an exception "Element tag name should be select".

WAIT !!! That's not the end of the world. Still we can make the dropdown work.

QATTS has solutions defined to all the problems in handling the dropdown. Refer to link  [Trouble Shoot](/studio/ui-elements/drop_down/trouble-shoot.md)

Now, lets see some questions / exception from communities [Properties Library](/studio/ui-elements/drop_down/properties-library.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 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.qatts.com/studio/ui-elements/drop_down.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.