Widely available Very useful for refining interaction affordances, but never rely on them as the only path to core functionality.

Interaction media queries

The any-hover CSS media feature can be used to test whether any available input mechanism can hover over elements.

PointerHoverInput modes

Browser support

Feature Desktop Mobile
Chrome
Edge
Firefox
Safari
Chrome Android
Safari iOS
css.at-rules.media.any-hover
41
16
64
9
41
9
CSS at-rule
any-pointer

The any-pointer CSS media feature tests whether the user has any pointing device (such as a mouse), and if so, how accurate it is.
41
12
64
9
41
9
hover

The hover CSS media feature can be used to test whether the user's primary input mechanism can hover over elements.
38
12
64
9
50
9
pointer

The pointer CSS media feature tests whether the user has a pointing device (such as a mouse), and if so, how accurate the primary pointing device is.
41
12
64
9
50
9
1+Supported (version) Not supported ※Has note Sub-feature descriptions sourced from MDN Web Docs (CC BY-SA 2.5)
Notes 1 item(s)
Implementation note
  • Before Chrome 41, the implementation was buggy and reported `(hover: none)` on non-touch-based computers with a mouse/trackpad. See bug 40397980.
Notes 1 item(s)
Implementation note
  • On some Android devices, such as certain Samsung models, the `(hover: hover)` media query may incorrectly match. See bug 41445959.

Syntax

CSS 
@media (hover: none) {
  .tooltip { display: none; }
}
@media (pointer: coarse) {
  button { min-height: 44px; }
}

Live demo

Hover Support

CSS Hover support demo.

PreviewFullscreen

Pointer: Coarse Support

CSS Pointer: coarse support demo.

PreviewFullscreen

Pointer: Fine Support

CSS Pointer: fine support demo.

PreviewFullscreen

Use cases

  • Hover enhancements

    Add hover-only polish on devices that support it while keeping the base interaction available elsewhere.

  • Touch-friendly sizing

    Adjust spacing and affordance density when coarse pointer input is likely.

Cautions

  • Devices can have multiple input modes, so any-pointer and hover behavior may not be as binary as expected.
  • Do not hide essential controls behind hover-only behavior.

Accessibility

  • Core actions must remain available to keyboard, touch, and assistive technology users regardless of pointer hints.
  • Use interaction queries to enhance usability, not to remove alternate access paths.

Related links