This page has been flagged with the following issues:
W3C Working Draft
Dispatched when a pointer leaves the state of having a non-zero value for the buttons property.
|Default action||Varies: when the pointer is primary, all default actions of the mouseup event|
For mouse, this is when the device transitions from at least one button depressed to no buttons depressed. For touch, this is when physical contact is removed from the digitizer. For pen, this is when the pen is removed from physical contact with the digitizer.
For input devices that do not support hover, a user agent must also fire a pointerout event after firing the pointerup event.
Needs Examples: This section should include examples.
Some pointer devices, such as mouse or pen, support multiple buttons. In the DOM Level 3 Events Mouse Event model, each button press produces a mousedown and mouseup event.
Pointer Events do not fire overlapping pointerdown and pointerup events when an additional button is depressed while another button on the pointer device is already depressed. For detecting these cases, see Chorded Button Interactions in the PointerEvents specification.
|Pointer Events||Working Draft||3.2.3|
|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: MSPointerUp|