docs.rodeo

MDN Web Docs mirror

Element: pointerout event

{{APIRef("Pointer Events")}} 

The pointerout event is fired for several reasons including: pointing device is moved out of the hit test boundaries of an element; firing the {{domxref("Element/pointerup_event", "pointerup")}}  event for a device that does not support hover (see {{domxref("Element/pointerup_event", "pointerup")}} ); after firing the {{domxref("Element/pointercancel_event", "pointercancel")}}  event (see {{domxref("Element/pointercancel_event", "pointercancel")}} ); when a pen stylus leaves the hover range detectable by the digitizer.

pointerout events have the same problems as {{domxref("Element/mouseout_event", "mouseout")}} . If the target element has child elements, pointerout and pointerover events fire as the pointer moves over the boundaries of these elements too, not just the target element itself. Usually, {{domxref("Element/pointerenter_event", "pointerenter")}}  and {{domxref("Element/pointerleave_event", "pointerleave")}}  events’ behavior is more sensible, because they are not affected by moving into child elements.

Syntax

Use the event name in methods like {{domxref("EventTarget.addEventListener", "addEventListener()")}} , or set an event handler property.

addEventListener("pointerout", (event) => { })

onpointerout = (event) => { }

Event type

A {{domxref("PointerEvent")}} . Inherits from {{domxref("Event")}} .

{{InheritanceDiagram("PointerEvent")}} 

Event properties

This interface inherits properties from {{domxref("MouseEvent")}}  and {{domxref("Event")}} .

Examples

Using addEventListener():

const para = document.querySelector("p");

para.addEventListener("pointerout", (event) => {
  console.log("Pointer moved out");
});

Using the onpointerout event handler property:

const para = document.querySelector("p");

para.onpointerout = (event) => {
  console.log("Pointer moved out");
};

Specifications

{{Specifications}} 

Browser compatibility

{{Compat}} 

See also

In this article

View on MDN