---
title: "Popover"
slug: popover
category: component
type: documentation
version: 20.0.0
tokens: 1476
source: https://ovh.github.io/design-system/v20.0.0/llms/react-components-popover--documentation.txt
---
# Popover
_**Popover** component is triggered by click and is used to provide additional information to the user in a new temporary surface that overlays the page_
## Overview
A **Popover** will provide additional information to the user in a clear and concise way.
It is commonly used to appear by click, thus crucial information should not be displayed in the **Popover**.
| | |
|---|---|
| Name | Popover |
| Also known as | Complex Tooltip |
| Design | https://www.figma.com/design/9jDDTcR4a9jPRFcdjawAlf/ODS---UI-Kit?node-id=49-8447 |
| Source | https://github.com/ovh/design-system/tree/master/packages/ods-react/src/components/popover |
## Usage
A **Popover** is used to provide an explanation for a user interface element.
It can include interactive elements such as a button or a link.
### Tooltip vs Popover
- Both components look similar but a [Tooltip](https://ovh.github.io/design-system/v20.0.0/components/tooltip) is displayed on hover and focus while **Popover** is triggered by click.
- Tooltips are commonly used for shorter explanations, while longer text / complex UIs would suit a popover better.
- Use a popover when you need to insert interactive elements such as Button.
- A popover can be dismissed if an action button allows it.
### Dos & Don'ts
**Do**
- Use a popover to display contextual information or options that are secondary to the main task
- Prefer a popover over a tooltip when the content is longer, interactive, or requires formatting (but keep it focused)
- Write a popover content using complete sentences
- Ensure the popover is positioned clearly and does not overlap with its trigger element
- Use a popover for lightweight content such as field explanations, secondary actions
**Don't**
- Don't place critical or mandatory information inside a popover. Users may miss it since it's only revealed on click
- Don't overload a popover with rich content like images, videos, or large interactive components. Use a Modal or Drawer instead
- Don't trigger a popover from non-obvious elements, the interactive element should clearly indicate it controls a popover
- Don't rely on popovers for persistent content since they're meant to be transient and dismissible
- Don't use a popover on elements that are already part of another complex interaction
### Best Practices in Context
1. **Popover**
2. **Content**
3. **Caret tip** - optional
4. **Trigger**
## Placement
**Popover** can be set in a certain position by default around its trigger.
**Popover** has automatic positioning feature. It can detect the edge of the browser so the container always stays visible on a page.
## Behavior
By default, a **Popover** is hidden to the user.
It triggers when the user clicks on the **Popover**'s trigger element such as a button.
The **Popover** can be closed or dismissed by clicking anywhere on the page outside the **Popover**'s container.
## Navigation
### Focus Management
Depending on the **Popover** trigger used (e.g., a button or a link), refer to that component's documentation for its keyboard interaction.
When the **Popover** is opened, it gains focus automatically. Focus remains within the **Popover** until it is closed.
Closing it returns focus to the trigger element.
### General Keyboard Shortcuts
Pressing `Escape` closes the currently opened **Popover**.
Pressing `Tab` moves focus forward through the focusable elements inside the **Popover**.
Pressing `Shift` + `Tab` moves focus backward within the **Popover**.
## Accessibility
To ensure proper accessibility, **Popover** component must specify its content nature using appropriate ARIA attributes.
### Specify the Popover's content nature
Update the content type on the **Popover Trigger**, which is set by default to `aria-haspopup="dialog"`.
Content Type
ARIA Attribute