Popover

For lightweight, contextual content or actions: Use Popovers to show information or actions directly related to a specific trigger (Button, icon, text).
When you want to keep users in context: Popovers are non-blocking and allow users to stay on the same screen without major interruptions.
To display additional details or previews on demand: For example, previewing user profile details on hover or click.
When you need more space than a tooltip, but less than a Dialog: Popovers can hold controls like Buttons, which can provide additional links to more information or confirmative actions like a soft (non-destructive) delete.

Brief, passive hints on hover/focus with no controls inside: use Tooltip.
Full attention, blocking flow, or critical decisions: use Dialog / Alert dialog or a dedicated page.
Choosing from a list of commands or values: use Menu or Select, not a generic Popover.

Do anchor the Popover clearly to a trigger element.
Do use a Popover for secondary or optional tasks as they should enhance the primary workflow, not interrupt it.
Do be mindful of screen boundaries and reposition the Popover if necessary as it should be fully visible when triggered without the user having to scroll to see it.
Don’t block essential content behind the Popover, or make sure the user can move the Popover to see the content.
Don’t allow more than one Popover to be displayed at a time.

Non-modal overlay anchored to a trigger; dismisses on outside click and Escape unless the design requires persistent multi-control content.
Repositions to remain in the viewport; may allow drag in implementations that support it—don’t obscure essential content without a way to reveal it.

Button or subtle text trigger; compact forms (Input, small Button); not a substitute for Menu command lists.

Documentation Index