- From: Rick Byers via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Sep 2017 14:14:08 +0000
- To: public-pointer-events@w3.org
Note that this API would obviously be required to work beyond long after the associated `PointerEvent` had been dispatched. I imagine developers would save the "current pointer" from a `pointerdown` listener, and invoke `tryDisableTouchActions` on it in a timer callback. One downside to this is that it could lead to developers keeping `PointerEvent` instances alive longer than necessary (eg. not clearing on `pointerup`), which could in turn keep an otherwise removed section of the DOM alive in RAM (due to the reference from `Event.target`). It's tempting to design a more stateless API (more like `Element.setPointerCapture` which takes a `pointerId`) but that would have the downside of being racey in scenarios where a user quickly flicks multiple times on different elements. Really I think we'd want an API that is somehow tightly coupled to a specific active pointer sequence, not just a `pointerId`. @staktrace @smaug---- @patrickkettner @patrickhlauke @dtapuska @NavidZ @mustaqahmed thoughts? -- GitHub Notification of comment by RByers Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/216#issuecomment-328114441 using your GitHub account
Received on Friday, 8 September 2017 14:14:04 UTC