-
Notifications
You must be signed in to change notification settings - Fork 160
"lostpointercapture" doesn't fire when releasing multiple pointer captures #188
Comments
This was on event listeners for two filled SVG paths, if it matters (#134). |
Also, it appears to be actually not releasing the pointer capture, beyond just not firing the event. |
The logic in https://github.com/jquery/PEP/blob/da854e479653a6ac367a3f031568923e09871a2e/src/dispatcher.js#L308-310 looks bugged. It's setting a listener across the entire document to release the pointer capture when any pointer is released? And it's only tracking one implicit release across the entire dispatcher? (This also explains why testing with multitouch causes a leak of event listeners on |
And shouldn't |
It seems to me that implicit pointer cature release checks would make more sense as part of the dispatchers around https://github.com/jquery/PEP/blob/da854e479653a6ac367a3f031568923e09871a2e/src/dispatcher.js#L162 and https://github.com/jquery/PEP/blob/da854e479653a6ac367a3f031568923e09871a2e/src/dispatcher.js#L182, checking for a pointer capture target override and then releasing the capture. |
I've been working on non-pointer-oriented projects for the last three months - I'm drifting back into pointer-oriented projects now, so I'm putting this back on my plate. |
PEP has now entered emeritus status at the OpenJS Foundation. This repository is now archived. |
Tested on my Acer C720P Chromebook, by touching two elements that setPointerCapture on pointerdown, and trust implicit pointer release for losing the capture - note how after "up", "out", and "leave", lostpointercapture does not fire for pointerId 3:
The text was updated successfully, but these errors were encountered: