Re: [pointerevents] Lost pointer issue - spec or browser bug? (#407)

> My workaround is to look out for a subsequent `pointermove` with a `.buttons` of 0 and synthesize a `pointercancel` if the pointer is currently considered 'down'.

In case anyone is doing the same thing, you'll need to work around Firefox, where `.buttons` is always 0 for touch-based pointer events.

GitHub Notification of comment by jakearchibald
Please view or discuss this issue at using your GitHub account

Sent via github-notify-ml as configured in

Received on Tuesday, 7 September 2021 13:15:07 UTC