Hover Card
Data displayShows supplementary preview content when a user hovers over or focuses its trigger.
Try it
Add to your project
npx shadcn@latest add https://luv-jeri.github.io/cojeev-ui/r/hover-card.jsonThe command includes the component’s shared dependencies. Your project keeps editable source files.
Include the complete example
This example also composes button, avatar, typography. Install its parts together:
npx shadcn@latest add https://luv-jeri.github.io/cojeev-ui/r/hover-card.json https://luv-jeri.github.io/cojeev-ui/r/button.json https://luv-jeri.github.io/cojeev-ui/r/avatar.json https://luv-jeri.github.io/cojeev-ui/r/typography.jsonUsing hover card
Use HoverCardTrigger for a link or focusable target and HoverCardContent for a brief preview.
Keep the destination and essential information available in the main interface.
API
Compose the exported parts below. The prop types are read from the React source during the registry build.
Native element or underlying primitive props are inherited where declared, including accessible labels, event handlers and refs.
HoverCardProps
Accepts the native or primitive props declared by its exported TypeScript type.
HoverCardTriggerProps
Accepts the native or primitive props declared by its exported TypeScript type.
HoverCardPortalProps
Accepts the native or primitive props declared by its exported TypeScript type.
HoverCardContentProps
| Prop | Type | Required |
|---|---|---|
portal | boolean | No |
Accessibility
Treat hover-card content as supplementary; use a Popover or Dialog when users must interact with or reliably access the content.
States and appearance
For conditional content, keep a MotionPresence boundary around keyed MotionSurface children. The shared entrance and exit states work with native primitives and respect your motion preference.
Try pointer and keyboard interaction, and switch the appearance control in the navigation to compare light and dark mode. Motion respects reduced motion preferences.