artifactExperience & interface

Popover

A popover is a transient surface positioned in relation to a trigger that provides contextual information or controls without permanently occupying the layout.

Download Markdown (.md)

01What it means

A popover appears above other content and is usually anchored to the element that invoked it. Unlike a tooltip, it may contain interactive controls; unlike a modal dialog, it does not inherently require the rest of the interface to become inert. Its dismissal and focus behavior depend on its purpose.[1][2]

02Why it matters

Popovers keep secondary actions or details close to their context, reducing navigation. Clear boundaries between popovers, tooltips, menus, and dialogs help teams implement the right semantics and keyboard behavior rather than treating every floating panel alike.

03When to use it

Use a popover for compact contextual controls or details that users can leave without resolving. Prefer inline disclosure for essential content, a menu for a list of actions, a tooltip for brief noninteractive help, and a dialog when a focused task must interrupt the page.

04How it works

  1. Define the trigger, purpose, content, and whether the surface is light-dismissed or explicitly closed.
  2. Anchor the surface near its trigger while allowing placement to change near viewport edges.
  3. Expose expanded state and an accessible name through native semantics or appropriate attributes.
  4. Set focus behavior according to whether the popover contains interactive controls.
  5. Test keyboard opening and closing, outside interaction, zoom, clipping, and trigger removal.

05A practical example

Example

Selecting a filter button opens a popover containing three compact filter controls. The panel is anchored to the button, exposes its open state, stays within the viewport, and closes on Escape while returning focus to the filter button.

06Where it breaks

Popover placement becomes fragile in small or zoomed viewports, and transient content can be missed or clipped by containers. Dismissal rules that are convenient for pointer users may cause keyboard or screen-reader users to lose work.

Common mistakes

  • Calling every floating surface a popover without defining its semantics.
  • Putting interactive controls in a tooltip.
  • Closing the popover whenever focus moves into its content.
  • Positioning it off-screen or far from the invoking control.

07Sources

  1. Popover APIMDN Web Docs · Technical documentationPopover API
  2. PopoversApple · Institutional guidelinePopovers
View saved topics

Start typing to search titles, definitions, categories, and frameworks.