Cursor shapes are ephemeral cues that vanish when the pointer moves away

What it is

A cursor shape is an ephemeral state cue: it exists only while the pointer remains in a relevant location, the window has focus, and the person sees it. It disappears when the pointer moves away, is obscured, or leaves the screen, so it complements immediate action cues but cannot alone carry state that must be remembered or revisited.

Why it happens

The shape is computed from current hit testing and reverts to default on leaving the region, and that computation and rendering is normally tied directly to the pointer-move event itself — no event, no new shape, and therefore no "memory" independent of where the pointer currently sits. It places information near the focus of attention with almost no layout cost, at the price of having no history, no fixed place to look back at, and no text to check against later. If someone misses the brief moment a shape appears, their only recourse is to hover again or fall back on some other, more persistent cue — which means an ephemeral cue is structurally hostile to two needs: being looked back at, and being shared. In a screen-share, screen recording, or any session where a second person is watching the same view, only the person holding the input device sees the cursor change in real time; the viewer can be looking at the exact same screen and still miss it entirely because of frame rate or a moment of divided attention.

Where it stops holding

Transient cues are efficient for low-risk, one-off actions, but they clearly fall short for permission, save state, upload progress, or complex modes, because those states need to be readable later — by someone who looked away, by a viewer joining midstream, or by an offline record such as a screenshot or recording — and a cursor shape leaves nothing behind once the pointer moves on. Remote desktops, screen sharing, and low-frame-rate recording are exactly where this boundary shows up most clearly: a presenter relies on a cursor-shape change to signal "I just clicked here," and the viewer's end never receives that frame at all because of transmission latency or sampling interval — the cue might as well never have existed for them.

Applying it

• Use cursor shape for what can happen right now, while keeping important state in persistent labels, selections, or status areas — the two should divide the work, not substitute for each other.
• Put repeat-discoverable actions in stable controls or menus rather than requiring memory of a cursor shape that flashed by once.
• Give mode changes and irreversible actions more durable, accessible confirmation; do not let their only signal be a shape that vanishes the instant the pointer moves.
• How to check: play back a screen recording of a complete task frame by frame and look for any critical state change communicated solely through a brief cursor-shape switch — if pausing or lowering the frame rate makes that information unreadable, it needs a more durable form of expression.

Related

• Same group: C1.19.1 Cursor-shape changes communicate available actions, such as resize arrows and grab hands · C1.19.3 A busy cursor signals system occupation, not position feedback · C1.19.4 Cursor-shape language depends on platform conventions and is not guaranteed cross-platform · C1.19.5 Cursor colour and contrast must remain discernible on light and dark backgrounds
• Nearby: D1 Output and feedback channels · E1 Interface elements and controls
• Search terms: ephemeral feedback · cursor state · visibility