Occurs when pointer capture previously held by this element moves to another element or elsewhere.
Note PointerCaptureLost might fire instead of PointerReleased. Don't rely on PointerPressed and PointerReleased events always occurring in pairs. To function properly, your app must listen for and handle all events that represent likely conclusions to the Press action, and that includes PointerCaptureLost. A pointer can lose capture either because of user interactions or because you programmatically captured another pointer or released the current pointer capture deliberately.
There is no event that fires when a pointer is successfully captured. To capture a pointer, you call the CapturePointer method, and this is usually done within the context of an event handler for other pointer events. For more info on how to capture a pointer and why you might want to do so, see CapturePointer or Responding to mouse interaction.
PointerCaptureLost is a routed event. For more info on the routed event concept, see Events and routed events overview.
PointerCaptureLost supports the ability to attach event handlers to the route that will be invoked even if the event data for the event is marked Handled. See AddHandler.
Minimum supported client
Minimum supported server
|Windows Server 2012|
- Quickstart: Touch input
- Responding to mouse interaction
- XAML user input events sample