> For the complete documentation index, see [llms.txt](https://matanya.gitbook.io/vue-tables-2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://matanya.gitbook.io/vue-tables-2/columns-visibility.md).

# Columns Visibility

#### Columns Dropdown

If you would like to enable the user to control the columns' visibility set the `columnsDropdown` option to `true`. This will add a dropdown button to the left of the per-page control. The drop down will contain a list of the columns with checkboxes to toggle visibility.

#### Responsive Columns Display

The `columnsDisplay` option allows you control over columns visibility depending on window size.
 Columns will only be shown when the window width is within the defined limits.

It accepts key-value pairs of column name and device.
 Possible values are: 

* mobile (x < 480)
* mobileP (x < 320)&#x20;
* mobileL (320 <= x < 480)
* tablet (480 <= x < 1024)
* tabletP (480 <= x < 768)
* tabletL (768 <= x < 1024)
* desktop (1024 <= x < 1280)
* desktopLarge (1280 <= x < 1920)
* desktopHuge (x >= 1920)

&#x20;All options can be preceded by the logical operators `min`,`max`, and `not` followed by an underscore.

For example, a column which is set to `not_mobile` will be shown when the width of the window is greater than or equal to 480px, while a column set to `max_tabletP` will only be shown when the width is under 768px

This option can work in conjunction with the `columnsDropdown` option, so by default only visible columns will be checked in the dropdown list

{% hint style="info" %}
The `columnsDropdown` option can work in conjunction with `columnsDisplay`. The rule is that as long as the user hasn't toggled a column himself, the rules you have declared in `columnsDisplay` takes precedence. Once the user toggled a column, he is in charge of columns' visibility, and the settings of `columnsDisplay` are disregarded.
{% endhint %}


---

# 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://matanya.gitbook.io/vue-tables-2/columns-visibility.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.