Tooltip
Native Versus
A side-by-side comparison: a button with the native title on the left, a custom tooltip on the right — arrowed, instant and reachable from the keyboard.
What you can change
- the text of both tooltips through tip
- the button captions through nativeLabel and customLabel
- the captions under the buttons and the closing line: nativeCaption, customCaption, note
A link for your AI agent: preview, code and instructions.
Preview
Use it with AI
- 1. Copy the link.
- 2. Write to your agent in your own words and drop the link into the sentence.
- 3. The agent opens the link and installs the component from the registry.
put this on the home page as the hero:
https://vibeui.ru/c/tooltip-002?lang=en&theme=dark
Not sure where to paste it? Step-by-step guide
Show the full instructions
What the link says, spelled out. Use it when your agent cannot open links — paste this text instead.
Loading…
For developers
The install command lives in the “Component source” block below — a signed link that stays valid for 24 hours.
Technical notes
The component is self-contained: one file, no dependencies, its own palette in local variables --vibeui-tooltip-002-*. It is a server component: both tooltips rest on :hover and :focus-within, no JS is needed. The left cell is deliberately left native — the title attribute shows the system tooltip after a second or so, with no arrow and no reaction to Tab. The right one is assembled by hand: the tail is a rotated square in the same colour, the opening is duplicated by focus, and the link to the button is declared through aria-describedby.
Tags
- tooltip
- comparison
- accessibility
- native
Component source
The same file your agent installs. Here in case you would rather copy it by hand.
Loading…