This page has been flagged with the following issues:
W3C Working Draft
Dispatched when either (1) the user agent has determined that a pointer is unlikely to continue to produce events (e.g., due to a hardware event), or (2) after having fired the pointerdown event, the pointer is subsequently used to manipulate the page viewport (e.g., panning or zooming).
A user agent will also fire a pointerout event after firing the pointercancel event.
Needs Examples: This section should include examples.
This event occurs when the pointer (touch or pen contact) is removed from the system. Here are common reasons why this might happen:
- A touch contact is canceled by a pen coming into range of the surface.
- The device doesn't report an active contact for more than 100ms.
- A mapping for a device's monitor changes while contacts are active. For example, the user changes the position of a screen in a two screen configuration.
- The desktop is locked or the user logged off.
- The number of simultaneous contacts exceeds the number that the device can support. For example, if a device supports only two contact points, if the user has two fingers on a surface, and then touches it with a third finger, this event is raised.
|Pointer Events||Working Draft||3.2.4|
|Feature||Chrome||Firefox (Gecko)||Internet Explorer||Opera||Safari|
|Basic Support||?||?|| ?
|Feature||Android||BlackBerry||Chrome for mobile||Firefox Mobile (Gecko)||IE Mobile||Opera Mobile||Opera Mini||Safari Mobile|
|Internet Explorer||10||Supported as: MSPointerCancel|
This article contains content originally from external sources.
Portions of this content come from the Microsoft Developer Network: Article