Skip to main content
Pointer Events

Starting with Windows 8, Internet Explorer supports W3C Pointer Events for handling user input. Pointer events are modeled after traditional mouse events, except they use the abstract concept of a pointer to apply across all user input modalities, including mouse, touch, and pen. Use pointer events to create a seamless user experience across user input methods by writing to a single set of events that work across hardware capabilities.

Pointer events and the PointerEvent object

The PointerEvent object inherits from MouseEvent, and is dispatched upon similar user interactions.

Mouse eventCorresponding pointer event
mousedown pointerdown
mouseenter pointerenter
mouseleave pointerleave
mousemove pointermove
mouseout pointerout
mouseover pointerover
mouseup pointerup


The PointerEvent object provides all the usual properties expected in mouse events (such as clientX / clientY coordinates, the target element, and button / buttons properties), as well as these additional properties to help you differentiate between input types and characteristics:

PointerEvent propertyDescription


The height (magnitude on the Y axis), in CSS pixels, of the contact geometry of the pointer.


Returns whether the pointer associated with the event is the primary pointer for the current mouse, touch, or pen interaction.


The unique identifier of the contact for a touch, mouse or pen.


Returns whether the source of the event is touch, pen, or mouse.


Returns the normalized pressure of the pointer input in the range of [0,1], where 0 and 1 represent the minimum and maximum pressure the hardware is capable of detecting, respectively.


Returns the angle between the Y-Z plane and the plane containing the pen axis and the Y axis in the range of -90 to +90. A positive X tilt is to the right.


Returns the angle between the X-Z and transducer-X planes. A positive Y tilt is toward the user.


Returns the width (magnitude on the X axis), in CSS pixels, of the contact geometry of the pointer.


Mouse compatibility

After firing pointer events, IE fires mouse events for the primary contact (for example, the first finger on the screen). This enables existing websites based on mouse events to continue to work correctly.

In contrast to a mouse, it's possible to have multiple pointers on the screen at one time (for example, with multi-touch hardware). In these scenarios, a separate pointer event fires for each point of contact, making it easier to build multi-touch-enabled sites and apps.

Feature detection and touch support testing

Use the PointerEvent interface to test for pointer event support:

if (window.PointerEvent) {
  // Pointer events are supported.

Be aware that pointer events feature detection doesn't indicate if the device itself supports touch or pen input. The PointerEvent property only checks if the platform will fire pointer events for whatever hardware is present in the system.

To test for touch capability and multi-touch support, use the maxTouchPoints property:

// Test for touch capable hardware 
if(navigator.maxTouchPoints) { ... }

// Test for multi-touch capable hardware
if(navigator.maxTouchPoints && navigator.maxTouchPoints > 1) { ... }

// Check the maximum number of touch points the hardware supports
var touchPoints = navigator.maxTouchPoints;

Controlling for default touch handling

Starting with Windows 8, IE provides default handling for common touch interactions, including panning for scrollable regions, pinch zooming, and HTML5 drag and drop support for touch that is activated by a user interaction sequence of press, hold, and drag. You can use the touch-action CSS property to specify if and how a given page region can be manipulated by touch input and default touch handling behaviors.

The following style rule disables all default touch handling and directs all pointer events to JavaScript code:

touch-action: none;
See Controlling the default touch experience for more details.

Capturing pointer events on an element

In some cases, it’s useful to assign a specific pointer to an element to make sure the element continues to receive pointer events even if the contact moves off the element.

For example, if a UI button in your web app is touched and held, and the user's finger slides off the button before raising it (breaking the contact), the button might not receive the pointerup event. This could cause the button to stay depressed forever. By assigning the pointer to the button element, the button receives pointer events, including the pointerup event that signals the button to return to its initial state.

You can call the setPointerCapture method of an element object to assign a specific pointerId to that element:

window.addEventListener('pointerdown', pointerdownHandler, false);

function pointerdownHandler (evt) {;
When a pointer is captured to an element, the parent and ancestor elements receive a gotpointercapture event during capture and bubble phase.

The capture is released when the pointer is removed ( pointerup) or explicitly released by calling the releasePointerCapture method. There are also cases where the element could lose the capture. For example, if the touch moves outside the window or some other element captures the touch, the element that had the capture loses the capture. The element that lost the capture receives a lostpointercapture event.

Pointer cancellation

When using touch or pen input, sometimes pointers on the screen can be canceled. For example, if your screen supports no more than two simultaneous touch points and you add a third finger to the screen, one of the other points will be canceled because the hardware cannot track three points. Pointer cancellation is indicated by the pointercancel event. This gives you the chance to handle any necessary cleanup. For example, if your app maintains a pointer list, you can listen for the pointercancel event to know when to remove a given pointer from that list.

Compatibility notes

To comply with the Candidate Recommendation of the W3C Pointer Events specification, the Internet Explorer 11 implementation of pointer events has changed slightly from that of Internet Explorer 10. For the complete details, see Pointer Events updates in the IE Compatibility Cookbook.

The HandJSJavaScript polyfill provides a library you can use to write to the pointer event model across browsers that don’t yet support W3C Pointer Events. For a demo, see Creating an universal virtual touch joystick with Hand.JS.

API reference


Samples and tutorials

Make your site touch-ready
Pointers and Gestures sample

Internet Explorer Test Drive demos

Mandelbrot Explorer
Browser Surface
Touch Effects
Brick Breaker

IEBlog posts

W3C Transitions Pointer Events to Candidate Recommendation
Learning more about Pointer Events as the W3C publishes Last Call Working Draft
W3C Charters Pointer Events Working Group
Towards Interoperable Pointer Events: Evolving Input Events for Multiple Devices
Guidelines for Building Touch-friendly Sites
Handling Multi-touch and Mouse Input in All Browsers
Touch Input for IE10 and Windows Store apps


Pointer Events Specification

Related topics

Creating an universal virtual touch joystick working for all Touch models thanks to Hand.JS
Gesture Events
Hand.js: a polyfill for supporting pointer events on every browser
Scrolling and zooming with touch
Unifying touch and mouse: how Pointer Events will make cross-browsers touch support easy