[Web] Remove explicit reset from onPointerCancel

[j-piasecki]

Description

#4128 changed how handlers kept in the orchestrator are treated - those can now influence other handlers' state. When trying to use the Touchable component in the example app, I've noticed that other buttons become unresponsive after scrolling cancels the pressed button.

This turned out to be caused by an explicit reset call inside onPointerCancel. This caused the handler's state to go to UNDETERMINED between the change to CANCELED and the time the orchestrator runs cleanupFinishedHandlers. When the orchestrator goes over the handlers to clean, it ignores handlers that are not in a finished state. Since the gesture changed to UNDETERMINED, it was kept in the orchestrator after being canceled.

Note that the handler is still being reset by the orchestrator in a scheduled microtask.

Test plan

I replaced RectButtons on in the example app list with Touchables

Before	After
Screen.Recording.2026-04-29.at.13.02.06.mov	Screen.Recording.2026-04-29.at.13.01.27.mov

[Copilot]

Pull request overview

Fixes a web-specific orchestration edge case where Touchable (and similar handlers) could remain in the GestureHandlerOrchestrator after being cancelled, causing unrelated buttons to become unresponsive.

Changes:

• Removes the explicit reset() call from GestureHandler.onPointerCancel so handlers remain in CANCELLED until the orchestrator’s scheduled cleanup resets/removes them.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.