# `Events['hotspot:hover']`

> Contract 2.0.0 · package sha256 `a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e` · generated from `configurator-runtime.d.ts` by `services/onsite-scripter/scripts/build-contract-docs.mjs`; edit the source, not this file.

Property of [`Events`](Events.md) · stable · since 2.0.0

```ts
'hotspot:hover': {
  readonly hotspot: HotspotReference | null;
};
```

The badge under the pointer, else the badge with keyboard focus (`:focus-visible`), else null;
it fires when that changes, so content you show on hover also shows on focus (WCAG 1.4.13).
It fires at the DOM event, and 'hover' at its next pick, so either can come first: keep an
"on a badge" flag from this event rather than relying on their order.

## Fields

<a id="hotspot"></a>
### `hotspot`

```ts
readonly hotspot: HotspotReference | null;
```

## Generic-API test (spec 3.1)

| Rule | Result |
| --- | --- |
| 1. Neutral name | pass: `hotspot:hover` names no product |
| 2. A precedent | not recorded: no ledger row (coverage.json) names this member or its owner |
| 3. Two apps, or labs | pass: 21 apps (fleet cross-check: app-04c2774145, app-0c773a4ee3, app-37356bf09f, app-378d190f1b, app-4762caacdc, app-4fd23bc869, app-822bb9d6aa, app-8675b3225c and 13 more) |
| 4. The cheaper fix first | not recorded per member (Appendix B decides it per need) |