# Tooltip
Name a control or add a short hint on hover and keyboard focus.
A tooltip names a control or adds a short hint when the pointer rests on it or keyboard focus reaches it. Keep it to a few words of plain text.
```tsx title="basic.tsx"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
function Example() {
return (
Add to library
)
}
export { Example }
```
The tooltip starts open. Hover the button or reach it with Tab to show it again, and Escape closes it while focus stays on the button.
## Installation
```bash
npm install @ui-sdk/solid @ui-sdk/core
```
## Composition
Use the following composition to build a `Tooltip`:
```text
Tooltip
├── TooltipTrigger
└── TooltipContent
├── TooltipArrow
└── TooltipShortcut
```
Wrap the trigger and its hint in a tooltip. The arrow and the shortcut are optional.
The content has the `tooltip` role, and it's in the page from the start, hidden, so it names or describes its trigger before focus reaches it. It names a trigger without a name of its own, like a button with only an icon, and describes any other: one with text, an `aria-label` or a `title`. `type="label"` or `type="description"` overrides the guess. Keep it to plain text: a tooltip can't be focused, so links or buttons inside it can't be reached. For anything interactive, use a [Popover](/docs/solid/components/popover) or a [Hover Card](/docs/solid/components/hover-card).
## Usage
Import the parts and put them together:
```tsx
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
function Example() {
return (
ShareAnyone with the link can view
)
}
export { Example }
```
## Side
`side` picks where the tooltip opens: `top` by default. It flips to the other side when there isn't room, and shifts along the trigger to stay on screen. `data-side` says where it landed.
```tsx title="side.tsx"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
import { For } from "solid-js"
const sides = [
{ side: "top", label: "Top" },
{ side: "left", label: "Left" },
{ side: "right", label: "Right" },
{ side: "bottom", label: "Bottom" },
] as const
function Example() {
return (
{({ side, label }) => (
{label}Add to library
)}
)
}
export { Example }
```
Hover Top, Left, Right and Bottom. Each tooltip opens on that side of its button, or flips into the middle when there isn't room.
Add a `TooltipArrow` to point at the trigger. It follows the side the tooltip lands on, including after a flip.
```tsx
Add to library
```
## Anchor
Position the tooltip against something other than the trigger with `anchor`: an element, a CSS selector, a point like `{ x, y }`, or anything with `getBoundingClientRect()`. Here a small help button inside a field shows its tooltip along the whole field.
```tsx title="anchor.tsx"
import { Field, FieldLabel } from "@ui-sdk/solid/field"
import { Input } from "@ui-sdk/solid/input"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
import { createSignal } from "solid-js"
function Example() {
const [field, setField] = createSignal(null)
return (
Webhook URL
We send a POST request here for every new order.
)
}
export { Example }
```
Hover the help button. The tooltip opens below the Webhook URL field and lines up with its start, not with the button.
## Keyboard Shortcut
`shortcut` on the tooltip, like `"mod+s"`, is a hint for what the trigger's action is bound to, where `mod` is Command on Apple platforms and Control elsewhere. `TooltipShortcut` shows the keys for the platform, `⌘S` or `Ctrl+S`, hidden from screen readers, and the trigger gets `aria-keyshortcuts` so they hear it instead. A `TooltipShortcut` can show other keys with its own `shortcut`.
The tooltip doesn't bind the keys. Register the shortcut yourself with [`registerShortcut`](/docs/solid/utilities/shortcuts), as the example does, or use the `shortcut` of a component that binds keys, like a [Dialog](/docs/solid/components/dialog#keyboard-shortcut) trigger.
```tsx title="shortcut.tsx"
import { registerShortcut } from "@ui-sdk/core/shortcuts"
import {
Tooltip,
TooltipContent,
TooltipShortcut,
TooltipTrigger,
} from "@ui-sdk/solid/tooltip"
import { onSettled } from "solid-js"
import { useLog } from "./log"
function Example() {
const log = useLog()
onSettled(() => {
const offSave = registerShortcut("mod+s", () => log("Saved"))
const offShare = registerShortcut("mod+shift+e", () => log("Shared"))
return () => {
offSave()
offShare()
}
})
return (
log("Saved")}>
Save
log("Shared")}>Share
Share with your team
)
}
export { Example }
```
Hover Save or Share to read its shortcut, then press the button or the keys. The console logs Saved or Shared.
## Disabled Buttons
A natively disabled button can't receive focus, and some browsers send it no pointer events, so its tooltip never shows. When the tooltip explains why an action is unavailable, use `aria-disabled="true"` instead and ignore the button's presses yourself. The button stays in the Tab order, screen readers announce it as dimmed, and the tooltip explains what's missing. `disabled` on the tooltip turns the explanation off once the button works.
```tsx title="disabled-button.tsx"
import { Field, FieldLabel } from "@ui-sdk/solid/field"
import { Input } from "@ui-sdk/solid/input"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
import { createSignal } from "solid-js"
import { useLog } from "./log"
function Example() {
const log = useLog()
const [title, setTitle] = createSignal("")
const blocked = () => !title().trim()
return (
Post title
setTitle(value)} />
{
if (!blocked()) {
log(`Published “${title().trim()}”`)
}
}}
>
Publish
Add a title to publish
)
}
export { Example }
```
Hover or focus Publish to learn what's missing. Type a title, and Publish works and its tooltip goes away.
## Touch
Touch screens have no hover. A tap on a plain tooltip's trigger only presses it, and the tooltip stays closed, so don't hide anything important in a tooltip.
For an info button whose only job is the tip, add `toggleable`: pressing the trigger opens and closes the tooltip, with a finger, a mouse or the keyboard, and its text is announced when a press opens it. An outside press or Escape closes it too.
```tsx title="toggleable.tsx"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
function Example() {
return (
StorageFiles in the trash still use storage.12.4 of 15 GB used
)
}
export { Example }
```
Press the info button to open the tip, including on a touch screen. Press it again or anywhere else to close it.
## Keep Open on Press
Pressing the trigger closes the tooltip, so it doesn't cover what the press changed, and it stays closed until the pointer leaves. `closeOnPress={false}` keeps it open, like for a copy button whose tooltip turns into "Copied".
```tsx title="copy.tsx"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
import { createSignal } from "solid-js"
const command = "npm install @ui-sdk/solid"
function Example() {
const [copied, setCopied] = createSignal(false)
return (
)
}
export { Example }
```
Hover the copy button and press it. The tooltip stays open and changes to Copied.
## Truncated Text
To show a tooltip only when text is cut off, cancel the open in `onOpenChange` when the text fits. Compare `scrollWidth` with `clientWidth` in the callback. The tooltip repeats the name, so `type="label"` keeps screen readers from hearing it twice.
```tsx title="truncated.tsx"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
import { For } from "solid-js"
const files = [
"Quarterly report, final revised version for the board.pdf",
"Notes.txt",
"Design review recording, October 2nd.mp4",
"Budget.xlsx",
]
function FileRow(props: { name: string }) {
let text: HTMLSpanElement | undefined
return (
{
const span = text
if (open && span && span.scrollWidth <= span.clientWidth) {
details.cancel()
}
}}
>
{props.name}{props.name}
)
}
function Example() {
return (
{(file) => }
)
}
export { Example }
```
Hover or focus each file. Only names that are cut off open a tooltip.
## Controlled
Pass `open` and update it in `onOpenChange`. Every change carries a [reason](#reasons), like `trigger-hover`, `trigger-focus`, `trigger-press`, `escape-key` or `outside-press`. Call `details.cancel()` to stop it. To open the tooltip from anywhere, like a step in a guided tour, use a [controller](#controller).
```tsx title="controlled.tsx"
import { Checkbox, CheckboxIndicator } from "@ui-sdk/solid/checkbox"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
import { createSignal } from "solid-js"
import { useLog } from "./log"
function Example() {
const log = useLog()
const [open, setOpen] = createSignal(false)
let controls: HTMLDivElement | undefined
return (
)
}
export { Example }
```
Check Open, or hover Export. The console logs each change and its reason.
## Shared
A toolbar, a chart or a long list can share one tooltip instead of rendering one per item. Connect the triggers and the tooltip to one `createTooltipController()`, and the triggers can sit anywhere on the page. Each trigger passes a `payload`, here its label, and the content reads it from its state, since every part's `children` can be a function of its state. `TooltipContent` types the payload. The content renders before the first open, so handle an `undefined` payload.
Only the trigger that opened the tooltip is described by it, so give each trigger a name of its own, like an `aria-label`. The controller's `open()` takes a payload and an `anchor` too, and on an open tooltip, `open({ payload })` replaces the payload, like another trigger taking it over. `onPayloadChange` reports each change.
```tsx title="shared.tsx"
import {
createTooltipController,
Tooltip,
TooltipContent,
TooltipTrigger,
} from "@ui-sdk/solid/tooltip"
import { For } from "solid-js"
const icon = (markup: string) => () => (
)
const Bold = icon(
''
)
const Italic = icon(
''
)
const Underline = icon(
''
)
const formats = [
{ icon: Bold, label: "Bold" },
{ icon: Italic, label: "Italic" },
{ icon: Underline, label: "Underline" },
]
function Example() {
const tooltip = createTooltipController()
return (
{(format) => (
)}
>{(state) => state.payload}
)
}
export { Example }
```
Move along Bold, Italic and Underline. One tooltip follows the pointer and shows each button's label.
## Animation
The content has `data-starting-style` while it opens and `data-ending-style` while it closes. Transition from those states, and the tooltip stays mounted until its exit finishes. Put `transform-origin: var(--transform-origin)` on the content so it grows out of its trigger. A tooltip that opens at once, as the next one in a group does, gets `data-instant`, so skip the transition there.
```css
[data-slot="tooltip-content"] {
transform-origin: var(--transform-origin);
transition:
opacity 150ms ease-out,
scale 150ms ease-out;
&:is([data-starting-style], [data-ending-style]) {
opacity: 0;
scale: 0.9;
}
&[data-instant] {
transition: none;
}
}
```
For people who ask for less motion, drop the scale in a `prefers-reduced-motion` query and keep the fade. `onOpenChangeComplete` runs once the tooltip has finished opening or closing, after any animation, with the new open state.
```tsx title="animation.tsx"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
import { useLog } from "./log"
function Example() {
const log = useLog()
return (
log(open ? "Opening" : "Closing")}
onOpenChangeComplete={(open) => log(open ? "Open" : "Closed")}
>
Archive
)
}
export { Example }
```
Hover Archive, then move away. The tooltip grows out of the button and fades, and the console logs Opening, Open, Closing and Closed.
## Delay and Grouping
`delay` is how long the pointer rests on the trigger before the tooltip opens, 600 milliseconds by default. `closeDelay` is how long it stays once the pointer leaves the trigger and the tooltip, 0 by default. Keyboard focus opens it at once.
Tooltips group without a provider. Once one is open, or was a moment ago, hovering the next opens it at once, and only one is open at a time, so moving along a toolbar reads like one tooltip that follows the pointer. A tooltip that opened at once gets `data-instant`, so it can skip its animation.
`disabled` stops a tooltip from opening, while its trigger keeps working.
```tsx
```
## Offset
`sideOffset` is the gap to the trigger, 4 pixels by default. `alignOffset` shifts along it, `align` lines it up with the start, center or end of the trigger, and `collisionPadding` is the space kept from the edges of the window.
```tsx
```
## Container
Tooltips render in place and show in the top layer, so no ancestor clips or covers them. `container` renders the tooltip somewhere else, for iframes, shadow roots or a specific stacking context. See the shared [popup guide](/docs/solid/popups).
```tsx
```
## Custom Rendering
Every part takes `render`, a function that receives the props to spread and the part's state. See [Parts and Composition](/docs/solid/parts-and-composition) for prop merging and state-based rendering.
```tsx title="custom-rendering.tsx"
import { Tooltip, TooltipContent, TooltipTrigger } from "@ui-sdk/solid/tooltip"
function Example() {
return (
(
)}
>
Changelog
See what's new in 2.0
)
}
export { Example }
```
Hover Changelog. The trigger renders as a link, and its tooltip says where it goes.
A button can be a tooltip's trigger and another component's trigger at once. Render the tooltip's trigger as a `PopoverTrigger`, and the button opens the popover and is named by the tooltip:
```tsx
}>
Notifications...
```
## Styling
Use `data-side` and `data-align` to style the content and arrow for where they landed, and `data-instant` to skip the animation of a tooltip that opened at once. The trigger gets no state attributes of its own, since it's often another component's trigger too, like a menu's. Put `transform-origin: var(--transform-origin)` on the content so it scales from the trigger.
Each part has a `data-slot`, such as `tooltip-content`, and its state attributes are listed under [Data Attributes](#data-attributes).
### TooltipContent
- `--anchor-width`: Width of the anchor, usually the trigger. Use it to match widths.
- `--anchor-height`: Height of the anchor.
- `--available-width`: Space beside the popup, up to the viewport edge. Not inherited either.
- `--available-height`: Space between the anchor and the viewport edge. Use it for max-height. Not inherited, so a child that needs it copies it on the popup, like `[--list-height:var(--available-height)]`, and reads `max-h-(--list-height)`. The first popup registers both names for the whole page with `CSS.registerProperty`, so they don't inherit anywhere. A page that needs them to inherit calls it first, with `inherits: true`. An `@property` rule can't, since a registration in script wins.
- `--transform-origin`: The point on the anchor the popup opens from. Use it to scale from the right place.
- `--arrow-offset`: Where the anchor's center falls along the popup's edge, kept `arrowPadding` from the corners. Position a ::before arrow with it.
## Data Attributes
`TooltipTrigger` and `TooltipShortcut` have no state attributes.
### TooltipContent
`[data-slot="tooltip-content"]`
- `data-closed`: Present while the tooltip is closed, including while it animates out.
- `data-open`: Present while the tooltip is open.
- `data-starting-style`: Present for the first frame. Style the state you animate from.
- `data-ending-style`: Present while the tooltip animates out. Style the state you animate to.
### TooltipArrow
`[data-slot="tooltip-arrow"]`
- `data-closed`: Present while the tooltip is closed, including while it animates out.
- `data-open`: Present while the tooltip is open.
## API Reference
Props and callbacks are the same as below, as Solid props.
### Tooltip
- `container?` (`DocumentFragment | Element | null`): Renders the popup into this element instead of in place, like a container inside a shadow root or an iframe. On web components, a CSS selector. Nested popups stay inside their parent.
- `open?` (`boolean`): Whether the tooltip is open. Pass it to control the tooltip.
- `defaultOpen?` (`boolean`): Whether the tooltip starts open, when uncontrolled.
- `onOpenChange?` (`((open: boolean, details: ChangeDetails) => void)`): Runs when the tooltip wants to open or close. `details.reason` says why, and `details.cancel()` stops it.
- `onOpenChangeComplete?` (`((open: boolean) => void)`): Runs once the tooltip has finished opening or closing, after any animation.
- `onPayloadChange?` (`((payload: unknown, details: ChangeDetails) => void)`): Runs when the payload the content shows changes: a trigger with another payload opens the tooltip, or takes the open tooltip over, which fires no `onOpenChange`, and so does a controller's `open({ payload })` on the open tooltip. `details.cancel()` keeps the previous payload.
- `delay?` (`number`): Milliseconds the pointer rests on the trigger before the tooltip opens. While another tooltip is open, or was a moment ago, the next one opens at once, without a provider.
- `closeDelay?` (`number`): Milliseconds before the tooltip closes once the pointer leaves the trigger and the tooltip.
- `disabled?` (`boolean`): Stops the tooltip from opening. The trigger keeps working.
- `toggleable?` (`boolean`): Whether pressing the trigger opens and closes the tooltip, so touch screens can show it too. For info buttons whose only job is the tip. The text is announced when a press opens it.
- `closeOnPress?` (`boolean`): Whether pressing the trigger closes the tooltip. Set it to `false` to keep it open, like for a copy button whose tooltip turns into "Copied".
- `type?` (`"description" | "label"`): Whether the tooltip names its trigger (`"label"`) or adds a description to it (`"description"`). By default it names a trigger that has no name of its own, like an icon button, and describes any other.
- `shortcut?` (`string`): The keyboard shortcut of what the trigger does, like `"mod+s"`, as a hint. A `TooltipShortcut` shows it, and the trigger gets `aria-keyshortcuts`. It doesn't bind the keys: the trigger's own `shortcut`, or `registerShortcut`, does.
- `controller?` (`PopupController`): Opens, closes and inspects the tooltip from anywhere, and connects triggers outside it. Create one with `createTooltipController()`.
- `debug?` (`boolean`): Logs every state change with its reason to the console, in development builds.
### TooltipTrigger
A trigger outside the tooltip also takes `controller`.
- `payload?` (`unknown`): Data for the content to render when this trigger opens the tooltip, like the row it belongs to.
- `controller?` (`PopupController`): Connects a trigger outside the tooltip, like one per table row, to the tooltip with this controller.
### TooltipContent
- `side?` (`Side`): Which side of the anchor the popup opens on. Flips to the other side when there isn't room. Which side of the trigger the tooltip opens on.
- `align?` (`Align`): How the popup lines up with the anchor along that side. `start` and `end` follow the reading direction. How the tooltip lines up with the trigger along that side.
- `sideOffset?` (`number`): Gap between the anchor and the popup, in pixels. Gap between the trigger and the tooltip, in pixels.
- `alignOffset?` (`number`): Shift along the anchor, in pixels. Shift along the trigger, in pixels.
- `collisionPadding?` (`number`): Space to keep from the viewport edges, in pixels.
- `arrowPadding?` (`number`): Space to keep between the arrow and the popup's corners, in pixels.
- `anchor?` (`string | Anchor | null`): Positions the popup against this instead of its trigger: an element, a CSS selector, a point like `{ x, y }`, or anything with `getBoundingClientRect()`. It's read on every check, so it can move. A controller's `open({ anchor })` wins for that open.
- `container?` (`DocumentFragment | Element | null`): Renders the popup into this element instead of in place, like a container inside a shadow root or an iframe. On web components, a CSS selector. Nested popups stay inside their parent.
### TooltipArrow
Points at the trigger from the side the tooltip landed on. Renders a `div`.
### TooltipShortcut
- `shortcut?` (`string`): The keys to show. By default, the tooltip's `shortcut`.
### State
What render functions, state-based class names and slots receive, per part.
`TooltipTrigger`:
- `open` (`boolean`): Whether the tooltip is open from this trigger.
`TooltipContent`:
- `open` (`boolean`): Whether the tooltip is open. False while it animates out.
- `instant` (`boolean`): Whether it opened at once, because another tooltip was open a moment ago. Animations can skip.
- `payload` (`Payload | undefined`): The payload of the last open, from the trigger that opened it or a controller, typed as the controller's `Payload`.
`TooltipArrow`:
- `open` (`boolean`): Whether the tooltip is open. False as soon as it starts closing, while it still animates out.
`TooltipShortcut`:
- `text` (`string`): The shortcut formatted for this platform: `⌘S` on Apple platforms and `Ctrl+S` elsewhere. Empty without one.
### Reasons
`details.reason` says why the tooltip opened or closed.
- `trigger-hover` (`PointerEvent`): The pointer rested on a trigger, or left it, with hover opening.
- `trigger-focus` (`FocusEvent`): Keyboard focus reached a trigger that opens on focus, like a tooltip's.
- `trigger-press` (`MouseEvent | KeyboardEvent | TouchEvent`): Click, tap, Enter or Space on the part that opens, closes or toggles. Arrow keys that open a menu or submenu count too. A tap on a combobox's input that opens a sheet reports its `touchend`.
- `focus-out` (`KeyboardEvent | FocusEvent`): Focus left the layer, or Tab moved it out.
- `escape-key` (`KeyboardEvent`): Escape, or a submenu's close key (ArrowLeft in left-to-right layouts).
- `close-press` (`MouseEvent | KeyboardEvent | SubmitEvent`): A Close part was pressed, or a form with `method="dialog"` was submitted.
- `outside-press` (`MouseEvent`): A press outside the layer.
- `window-blur` (`FocusEvent`): The window lost focus.
- `back` (`Event`): Going back: the Android back button or gesture, or Backspace in an empty command input, which returns to the previous page.
- `imperative` (`none`): A controller or `api` call, or a property set on a web component.
For a payload change, it says what opened the tooltip or took it over.
- `trigger-hover` (`PointerEvent`): The pointer rested on a trigger, or left it, with hover opening.
- `trigger-focus` (`FocusEvent`): Keyboard focus reached a trigger that opens on focus, like a tooltip's.
- `trigger-press` (`MouseEvent | KeyboardEvent | TouchEvent`): Click, tap, Enter or Space on the part that opens, closes or toggles. Arrow keys that open a menu or submenu count too. A tap on a combobox's input that opens a sheet reports its `touchend`.
- `imperative` (`none`): A controller or `api` call, or a property set on a web component.
### Controller
Create one with `createTooltipController()` and pass it as `controller`, to the tooltip and to any
triggers outside it. `Payload` is the type of the data triggers and `open()` pass.
Every write method takes an optional `{ reason, event }`, passed to `onOpenChange`.
- `isOpen()` (`() => boolean`): Whether it's open. False as soon as it starts closing, while it still animates out.
- `setOpen(open, options?)` (`(open: boolean, options?: PopupChangeOptions | undefined) => boolean`): Opens or closes it. Returns false when the change was canceled or it was already open or closed.
- `open(options?)` (`(options?: (PopupChangeOptions & { payload?: Payload | undefined; anchor?: Anchor | undefined; signal?: AbortSignal | undefined; }) | undefined) => Promise<...>`): Opens it, and resolves once it closes, with why, how and any return value. Resolves exactly once and never rejects: on the next close from any source, when `signal` aborts, or with reason `"unmount"` when the component leaves the page.
- `close(options?)` (`(options?: (PopupChangeOptions & { returnValue?: string | undefined; }) | undefined) => boolean`): Closes it. `returnValue` is passed to the promise `open()` returned. Returns false when the close was canceled or it was already closed.
- `toggle(options?)` (`(options?: PopupChangeOptions | undefined) => boolean`): Opens it when it's closed, and closes it when it's open. Returns false when the change was canceled.
- `getPayload()` (`() => Payload | undefined`): The payload of the last open, from a controller or the trigger that opened it.
- `focus()` (`() => void`): Moves focus to the trigger that opened it last, or the first trigger.
### Events
Callbacks get the new state first, then the details.
| Prop | On | Receives |
| ---------------------- | --------- | --------------------------------------------------------------------------- |
| `onOpenChange` | `Tooltip` | `(open, details)`: the new state, and the [reason](#reasons) |
| `onOpenChangeComplete` | `Tooltip` | `(open)`, after the animation |
| `onPayloadChange` | `Tooltip` | `(payload, details)`: the content's new payload, and the [reason](#reasons) |
## Accessibility
The trigger is named or described by the tooltip, following the [WAI-ARIA tooltip pattern](https://www.w3.org/WAI/ARIA/apg/patterns/tooltip/). It opens on hover and on keyboard focus, and stays open while the pointer moves onto it.
### Keyboard
| Key | Does |
| ------------ | ---------------------------------------------------------------------------------------------- |
| Tab | Focus on the trigger opens the tooltip at once; focus leaving it closes the tooltip |
| Escape | Closes the tooltip and leaves focus on the trigger, without closing a dialog or menu around it |
| Enter, Space | Presses the trigger and closes the tooltip; on a `toggleable` trigger, opens and closes it |
### Tested Behavior
Every line below is an automated test.
**Pointer**
- Resting the pointer on the trigger opens the tooltip.
- The tooltip waits for its delay before opening.
- Leaving the trigger before the delay keeps the tooltip closed.
- Moving the pointer away closes the tooltip.
- The pointer can move onto the tooltip without closing it.
- Opening on hover leaves focus where it was.
- Pressing the trigger closes the tooltip and runs the button.
- After a press, the tooltip stays closed until the pointer comes back.
**Keyboard**
- Keyboard focus on the trigger opens the tooltip.
- Focus leaving the trigger closes the tooltip.
- Escape closes the tooltip and leaves focus on the trigger.
- Escape closes a tooltip opened by hover.
- Tab through the toolbar shows each tooltip in turn.
- A click that focuses the trigger doesn't open the tooltip from focus.
**Several tooltips**
- Only one tooltip is open at a time.
- Once the pointer has been away a while, the delay applies again.
**Positioning**
- The tooltip opens above the trigger.
- The tooltip flips below the trigger when there is no room above.
- The tooltip opens on the requested side.
- The arrow points at the middle of the trigger.
**A tooltip on a popover trigger**
- Hovering shows the tooltip, and pressing opens the popover instead.
- Escape closes the tooltip and leaves the popover open.
**Disabled buttons**
- Browsers send hover events to a disabled button.
- An aria-disabled trigger shows its tooltip on hover and focus and ignores presses.
**Animation**
- The tooltip animates in from its starting style.
- The tooltip stays in the page while it animates out.
**Hidden while closed**
- A class that sets display on the content doesn't show it while closed.
**Options and dismissal**
- Escape closes only a tooltip that keyboard focus opened inside a popover.
- The pointer can leave the trigger sideways on its way to the tooltip.
- With closeOnPress false, pressing the trigger keeps the tooltip open.
- Disabled tooltips never open.
- A tap on a plain tooltip's trigger only presses it.
Runs in React, Vue and web components.
Also tested:
**Enhancements**
- Focus returning to the trigger after its popover closes doesn't reopen the tooltip.
- Tooltips open at once after another one, without a provider.
- Focus coming back with the window doesn't reopen the tooltip.
- A controller opens the tooltip without moving focus.
- A trigger that's a disabled button warns in development.
**Shortcuts**
- A trigger connected through a controller shows its tooltip's shortcut in a Shortcut part.
**Toggleable**
- Pressing a toggleable trigger opens and closes the tooltip.
- Pressing outside closes a toggleable tooltip.
- Enter toggles the tooltip from the keyboard and keeps focus on the trigger.
- A press announces the tooltip's text to screen readers.
- A tap opens a toggleable tooltip on a touch screen.
Runs in React, Vue and web components.
Screen readers hear the same thing in each tested framework, recorded by a virtual screen reader:
- Announcements while tabbing through triggers with tooltips.
Runs in React, Vue and web components.