Detect Hover
JavaScript wrapper for hover
and any-hover
media queries.
Live detection test
Exports a reference to a singleton object (a micro state machine with an update function) with its state set to the results of the hover
and any-hover
media queries, as well as an update()
function which re-runs the tests and updates the object's state.
Note that detect-hover
is one of the micro state machines used by detect-it
to determine if a device is mouseOnly
, touchOnly
, or hybrid
.
For more information on the hover
and any-hover
media queries, please see the W3C Media Queries Level 4 specification. For information on browser compatibility, please see Can I Use matchMedia.
detectHover
micro state machine
const detectHover = {
hover: boolean,
none: boolean,
anyHover: boolean,
anyNone: boolean,
update() {...},
}
Installing detect-hover
$ npm install detect-hover
Using detect-hover
import detectHover from 'detect-hover';
detectHover.hover === true;
detectHover.none === true;
detectHover.anyHover === true;
detectHover.anyNone === true;
detectHover.update();
const detectHover = {
hover: undefined,
none: undefined,
anyHover: undefined,
anyNone: undefined,
}
Note that the update()
function is run once at the time of import to set the object's initial state, and generally doesn't need to be run again. If it doesn't have access to the window
or the browser doesn't support the matchMedia()
function (all modern browser do), then the state will be undefined
(detect-hover
will not throw an error). If detect-hover
doesn't have access to the window
at the time of import, you will have to call the update()
function manually at a later time to update its state.
Note that the hover on-demand value was removed from the July 6th 2016 W3C Media Queries Level 4 draft specification, but was included in the previous draft (January 26th 2016) of the spec. Any device that registers as having hover on-demand capabilities will show up as hover none
in detectHover
's state. As a side note, hover on-demand is pretty much useless for practical purposes, and Android touch only devices register that they can hover on-demand, which is achieved via a long press - I view this as a feature that is a bug.
Part of the detect-it
family