PointerEvent interface represents the state of a DOM event produced by a pointer such as the geometry of the contact point, the device type that generated the event, the amount of pressure that was applied on the contact surface, etc.
A pointer is a hardware agnostic representation of input devices (such as a mouse, pen or contact point on a touch-enable surface). The pointer can target a specific coordinate (or set of coordinates) on the contact surface such as a screen.
A pointer's hit test is the process a browser uses to determine the target element for a pointer event. Typically, this is determined by considering the pointer's location and also the visual layout of elements in a document on screen media.
Creates a synthetic—and untrusted—
This interface inherits properties from
A unique identifier for the pointer causing the event.
The width (magnitude on the X axis), in CSS pixels, of the contact geometry of the pointer.
The height (magnitude on the Y axis), in CSS pixels, of the contact geometry of the pointer.
The normalized pressure of the pointer input in the range
1represent the minimum and maximum pressure the hardware is capable of detecting, respectively.
The normalized tangential pressure of the pointer input (also known as barrel pressure or cylinder stress) in the range
0is the neutral position of the control.
The plane angle (in degrees, in the range of
90) between the Y–Z plane and the plane containing both the pointer (e.g. pen stylus) axis and the Y axis.
The plane angle (in degrees, in the range of
90) between the X–Z plane and the plane containing both the pointer (e.g. pen stylus) axis and the X axis.
The clockwise rotation of the pointer (e.g. pen stylus) around its major axis in degrees, with a value in the range
Indicates the device type that caused the event (mouse, pen, touch, etc.).
Indicates if the pointer represents the primary pointer of this pointer type.
Returns a sequence of all
PointerEventinstances that were coalesced into the dispatched
Returns a sequence of
PointerEventinstances that the browser predicts will follow the dispatched
pointermoveevent's coalesced events.
Pointer event types
PointerEvent interface has several event types. To determine which event fired, look at the event's
Note: It's important to note that in many cases, both pointer and mouse events get sent (in order to let non-pointer-specific code still interact with the user). If you use pointer events, you should call
event.preventDefault() to keep the mouse event from being sent as well.
This event is fired when a pointing device is moved into an element's hit test boundaries.
This event is fired when a pointing device is moved into the hit test boundaries of an element or one of its descendants, including as a result of a
pointerdownevent from a device that does not support hover (see
pointerdown). This event type is similar to
pointerover, but differs in that it does not bubble.
The event is fired when a pointer becomes active. For mouse, it is fired when the device transitions from no buttons pressed to at least one button pressed. For touch, it is fired when physical contact is made with the digitizer. For pen, it is fired when the stylus makes physical contact with the digitizer.
Note: For touchscreen browsers that allow direct manipulation, a
pointerdownevent triggers implicit pointer capture, which causes the target to capture all subsequent pointer events as if they were occurring over the capturing target. Accordingly,
pointeroutwill not fire as long as this capture is set. The capture can be released manually by calling
element.releasePointerCaptureon the target element, or it will be implicitly released after a
This event is fired when a pointer changes coordinates.
This event is fired when any of a pointer's properties change.
This event is fired when a pointer is no longer active.
A browser fires this event if it concludes the pointer will no longer be able to generate events (for example the related device is deactivated).
This event is fired for several reasons including: pointing device is moved out of the hit test boundaries of an element; firing the
pointerupevent for a device that does not support hover (see
pointerup); after firing the
pointercancel); when a pen stylus leaves the hover range detectable by the digitizer.
This event is fired when a pointing device is moved out of the hit test boundaries of an element. For pen devices, this event is fired when the stylus leaves the hover range detectable by the digitizer.
This event is fired when an element receives pointer capture.
This event is fired after pointer capture is released for a pointer.
Examples of each property, event type, and global event handler are included in their respective reference pages.
|Pointer Events |
BCD tables only load in the browser