Hover Card

Installation

Copy editable source into an initialized application:

pnpm dlx @simurgh-ui/cli add hover-card

For package consumption, import from the component subpath and load its optional recipe CSS:

React

import {
  HoverCard,
  HoverCardTrigger,
  HoverCardContent,
} from '@simurgh-ui/react/hover-card';
import '@simurgh-ui/styles/hover-card.css';

Vue

import {
  HoverCard,
  HoverCardTrigger,
  HoverCardContent,
} from '@simurgh-ui/vue/hover-card';
import '@simurgh-ui/styles/hover-card.css';

Angular

import { HoverCardComponent } from '@simurgh-ui/angular/hover-card';
import '@simurgh-ui/styles/hover-card.css';

Omit the component stylesheet for fully headless styling. CLI-copied components use the local path written to simurgh.json and the copied application styles instead of these package imports.

Purpose

Hover Card reveals a compact, labelled preview without requiring activation. Its trigger works with pointer hover and keyboard focus, and the card uses collision-aware positioning.

Default presentation: styled

The optional component stylesheet provides a complete default recipe, including visual hierarchy and interaction states. Consumers can override semantic tokens or omit the recipe.

Basic usage

Live component Hover Card ◆

Simurgh UI

Anatomy

The public component parts are listed in API surface below. Use only the parts needed by the example; compound components depend on their documented parent/child nesting.

State model

Controlled state remains the application’s source of truth and must be updated from every change event. Uncontrolled state reads its default only when the component mounts. Do not pass both forms of the same state at once.

Framework	Exact state contract and reset behavior
React	Controlled: open + onOpenChange. Uncontrolled: defaultOpen. Reset controlled state by assigning the initial value; reset uncontrolled state by changing a React key.
Vue	Controlled: v-model:open (open + update:open). Uncontrolled: defaultOpen. Reset the model ref to its initial value; reset uncontrolled state with a changed Vue :key.
Angular	No public two-way state binding is exposed.

React

const initialOpen = false;
const [open, setOpen] = useState(initialOpen);
const [resetKey, setResetKey] = useState(0);

<HoverCard open={open} onOpenChange={setOpen}>…</HoverCard>
<button onClick={() => setOpen(initialOpen)}>Reset controlled</button>
<HoverCard key={resetKey} defaultOpen={initialOpen}>…</HoverCard>
<button onClick={() => setResetKey((key) => key + 1)}>Reset uncontrolled</button>

Vue

<script setup lang="ts">
import { ref } from 'vue';
const initial = false;
const state = ref(initial);
const resetKey = ref(0);
</script>

<HoverCard v-model:open="state">…</HoverCard>
<button @click="state = initial">Reset controlled</button>
<HoverCard :key="resetKey" :defaultOpen="initial">…</HoverCard>
<button @click="resetKey++">Reset uncontrolled</button>

Keep hover-card content concise and nonessential. Use Dialog when the content requires a decision, form interaction, or modal focus management.

Examples

React

<HoverCard>
  <HoverCardTrigger>Simurgh UI</HoverCardTrigger>
  <HoverCardContent label="Simurgh UI profile">
    Accessible components for Angular, React, and Vue.
  </HoverCardContent>
</HoverCard>

Vue

<HoverCard>
  <HoverCardTrigger>Simurgh UI</HoverCardTrigger>
  <HoverCardContent label="Simurgh UI profile">
    Accessible components for Angular, React, and Vue.
  </HoverCardContent>
</HoverCard>

Angular

<simurgh-hover-card label="Simurgh UI profile">
  <button trigger>Simurgh UI</button>
  <p>Accessible components for Angular, React, and Vue.</p>
</simurgh-hover-card>

Accessibility

Preserve the documented composition and accessible names when wrapping or restyling this component. See accessibility and RTL guidance for keyboard, focus, labeling, and directionality requirements.

API surface

• React exports: HoverCard, HoverCardTrigger, HoverCardContent
• Vue exports: HoverCard, HoverCardTrigger, HoverCardContent
• Angular exports: HoverCardComponent

Import these public symbols from the component subpath shown in Installation. Framework-specific props, events, slots, directives, methods, defaults, and native-attribute behavior belong in the API tables on this page; use the linked source only to verify the current implementation.

React API reference

React

An inherited-attributes entry means the component accepts the complete named React native interface, including its event handlers and ARIA and data attributes. Remaining attributes are forwarded to the rendered element unless the component behavior described on this page overrides them.

HoverCard

Complete props type: PropsWithChildren<OpenProps>.

Prop	Type	Default / requirement
children	ReactNode	undefined
defaultOpen	boolean	undefined
onOpenChange	(open: boolean) => void	undefined
open	boolean	undefined

HoverCardTrigger

Inherited attributes: ButtonHTMLAttributes<HTMLButtonElement> & RefAttributes<HTMLButtonElement>.

Prop	Type	Default / requirement
children	ReactNode	undefined
ref	Ref<HTMLButtonElement> | undefined	undefined

HoverCardContent

Inherited attributes: HTMLAttributes<HTMLDivElement>.

Prop	Type	Default / requirement
children	ReactNode	undefined
label	string	undefined

Vue API reference

Vue

Boolean props without explicit defaults use Vue’s false default. Undeclared attributes follow the fallthrough behavior stated for each component.

HoverCard

Vue attribute fallthrough is enabled for the rendered root.

Prop	Type	Default / requirement
open	boolean	undefined
defaultOpen	boolean	false

Event	Payload
update:open	boolean

Slots: default.

Exposed methods: none.

HoverCardTrigger

Vue attribute fallthrough is enabled for the rendered root.

No declared props.

No emitted events.

Slots: none.

Exposed methods: none.

HoverCardContent

Vue attribute fallthrough is enabled for the rendered root.

Prop	Type	Default / requirement
label	string	'Additional information'

No emitted events.

Slots: none.

Exposed methods: none.

Angular API reference

Angular

Inputs and outputs use their public template names. Public methods are callable through a template reference or ViewChild. Native attributes apply to the documented template root or directive host; they are not automatically forwarded through component hosts.

HoverCardComponent

Component selector: simurgh-hover-card. The template’s first native element is span.

Input	Type	Default / requirement
label	string	'Additional information'

No outputs.

Content projection: [trigger], default.

Public method
setOpen(value: boolean): void

Composition contract

Follow the framework example as a structural contract. Root components own shared state; parts that consume that state must stay under the root (or be attached to projected descendants in Angular). Parts described as conditional are optional until their corresponding interaction or semantic region is used. Do not render a state-consuming part by itself.

Framework	Required parent/child relationship	Conditional parts	Supporting types
React	Render HoverCard as the ancestor. Nest the listed parts inside that root so they can read its shared state/context.	HoverCardTrigger, HoverCardContent are conditional parts: include only those needed by the documented anatomy. A trigger/control and its matching content/item are required when that interaction is used.	None.
Vue	Render HoverCard as the ancestor. Nest the listed parts inside that root so they can read its shared state/context.	HoverCardTrigger, HoverCardContent are conditional parts: include only those needed by the documented anatomy. A trigger/control and its matching content/item are required when that interaction is used.	None.
Angular	Create HoverCardComponent first and project descendants into its named regions.	[trigger], default are projection regions; default is the main body and named selectors such as [trigger] are required only for that interaction.	None.

Accessible names, descriptions, and form labels remain required whenever the component’s purpose cannot otherwise be determined, even when the corresponding visual part is optional.

Framework parity and differences

The adapters target the same user-visible behavior and accessibility contract. Their public shapes follow each framework’s conventions and are not expected to be symbol-for-symbol identical.

Concern	Contract
Public composition	React exports 3 parts, Vue 3, and Angular 1. These are intentional composition differences; use each framework’s example rather than translating symbol-for-symbol.
State and change events	React uses controlled/default props and callbacks for open; Vue uses v-model:open; Angular uses inputs and outputs.
Children and content	React uses children; Vue uses the slots listed above; Angular uses the documented content projection selectors.
Native attributes	React forwards the named native interface; Vue follows the stated fallthrough rule; Angular attributes apply to the component host unless an input, directive, or documented native root consumes them.
Imperative access	React forwards native refs; Vue exposes no methods; Angular exposes the listed class methods through a template reference or ViewChild.

These differences are intentional adapter design. Behavioral or accessibility differences not stated on this page are parity defects rather than supported variations.

Form integration

This component is not a form control and does not contribute a named value to FormData. Use it to structure or describe a form only when its purpose and accessibility guidance apply.

Supported states

The table distinguishes component behavior from application-owned presentation. “Not supported” means there is no public state contract for that adapter; do not invent one with an undocumented attribute. Keep status and error messages accessible when they are rendered outside the component.

State	React	Vue	Angular
Loading	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.
Empty	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.
Invalid	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.
Read-only	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.
Disabled	Supported with disabled={true} on the documented control or interactive part; its interaction is blocked. Disabled form controls are omitted from submission.	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.
Error	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.	Not supported by this component API; handle this state in surrounding application UI.

Styling contract

Styling contract

The selectors below are used by the published component recipe or emitted consistently by an adapter. Treat these as the supported styling surface. Element order, anonymous wrappers, and undocumented descendants are implementation details and should not be targeted.

Surface	Stable hooks
Recipe classes	.simurgh-content, .simurgh-item, .simurgh-trigger
Stable DOM parts	[data-slot="button"], [data-slot="checkbox"], [data-slot="hover-card-content"], [data-slot="hover-card-trigger"], [data-slot="input"], [data-slot="input-otp"], [data-slot="native-select"], [data-slot="pagination-link"], [data-slot="select-trigger"], [data-slot="toggle-group-item"], [data-slot="toolbar-button"]
Stable data attributes	[data-density], [data-simurgh-floating-content], [data-simurgh-floating-reference], [data-slot]
ARIA/state selectors used by the recipe	[aria-disabled]
CSS custom properties consumed	--simurgh-border, --simurgh-control-height, --simurgh-control-padding, --simurgh-foreground, --simurgh-radius, --simurgh-ring, --simurgh-shadow, --simurgh-surface

Prefer a semantic token override for theme-wide changes. Use the listed class or part selectors for a component-scoped override. When omitting recipe CSS, preserve state attributes and ARIA semantics even if your replacement styles use different selectors.

Customization

Load the optional component stylesheet for the default recipe, override semantic tokens for broad theme changes, or omit the recipe CSS for headless styling. See theming and styling hooks for import order, selectors, dark mode, RTL, and reduced-motion guidance.

Last verified on 2026-08-13 against Simurgh registry 0.1.1.

Related components

• Review the shared accessibility and RTL guidance and theming and styling hooks.
• Use the component chooser and component overview to compare related primitives.
• Inspect the registry manifest and framework source for React, Vue, or Angular.