`react-doctor/pointer-capture-needs-cancel-handler`

Captured pointer interaction has no cancellation path

Category: Bugs
Severity: warn
Source: oxlint-plugin-react-doctor
Framework: global
Enabled when: always
Default: Enabled

Validate the diagnostic

Confirm the reported code matches this rule before you edit it.

Confirm the reported code matches react-doctor/pointer-capture-needs-cancel-handler. Compare it with the Before example and verify the same API, framework, and execution context. Treat it as a false positive only when one of those conditions differs.

Compare the code

The corrected pattern shows a focused way to address the diagnostic.

Reported pattern

<div
  onPointerDown={(event) =>
    event.currentTarget.setPointerCapture(event.pointerId)
  }
  onPointerMove={moveDrag}
  onPointerUp={finishDrag}
/>;

Corrected pattern

<div
  onPointerDown={(event) =>
    event.currentTarget.setPointerCapture(event.pointerId)
  }
  onPointerMove={moveDrag}
  onPointerUp={finishDrag}
  onPointerCancel={cancelDrag}
  onLostPointerCapture={cancelDrag}
/>;

How to fix

Use the corrected pattern as a reference. Preserve behavior that the rule does not require you to change.

Copyable fix prompt

Copy this self-contained prompt into your coding agent after you confirm the diagnostic.

Fix every confirmed react-doctor/pointer-capture-needs-cancel-handler diagnostic in the current repository. Required change: - Handle onPointerCancel or onLostPointerCapture with the same cleanup used for pointer-up so interrupted drags cannot stay active.

Reference transformation:Before:

<div
  onPointerDown={(event) =>
    event.currentTarget.setPointerCapture(event.pointerId)
  }
  onPointerMove={moveDrag}
  onPointerUp={finishDrag}
/>;

After:

<div
  onPointerDown={(event) =>
    event.currentTarget.setPointerCapture(event.pointerId)
  }
  onPointerMove={moveDrag}
  onPointerUp={finishDrag}
  onPointerCancel={cancelDrag}
  onLostPointerCapture={cancelDrag}
/>;

Constraints: - Confirm the reported code matches the Before pattern. - Make the smallest change that fixes the root cause. - Preserve behavior and interfaces unrelated to this diagnostic. - Reuse existing project components, utilities, and conventions. - Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations. - Adapt identifiers and framework details instead of copying blindly. - Do not disable the rule or suppress matching code. Verification: - Run focused tests for the changed behavior. - Run React Doctor and confirm this diagnostic no longer appears. - Report the files changed and any checks you could not run.

More Bugs rules from the rules reference:

react-doctor/preact-no-children-length: Wrap with toChildArray(children) from preact before reading .length or calling array methods on props.children.
react-doctor/preact-no-react-hooks-import: Import hooks from `preact/hooks` (or `preact/compat`), not `react`: import { useState } from "preact/hooks"
react-doctor/preact-no-render-arguments: Drop render's positional params and read this.props / this.state inside render() instead
react-doctor/preact-prefer-ondblclick: Rename onDoubleClick to onDblClick on host elements: <li onDblClick={openInline}> — Preact uses DOM event names
react-doctor/preact-prefer-oninput: Replace onChange with onInput on text-like inputs: onInput={(e) => setQuery(e.currentTarget.value)}

react-doctor/pointer-capture-needs-cancel-handler