- From: Matt Rakow via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Feb 2019 19:27:50 +0000
- To: public-pointer-events@w3.org
How are the targets populated in the current list received from getCoalescedEvents? Presumably a hit test must be done at some point in order to generate those (Deferred until the coalesced event is dispatched maybe? Or until getCoalescedEvents is called?) Perhaps an alternative middle-ground approach might be to not fire the events immediately (still defer until the next frame or down/up/cancel as today) but at that time reconstruct and fire the sequence at the appropriate targets, with the appropriate enter/leave events interleaved? As currently written, I think the raw events proposal encounters the same issues since it seems to have the same rules for coalescing (just will generally tend to have less coalescing by virtue of being fired more frequently if the thread is idle)? I'd also hate to give up frame-aligned coalescing for scenarios that are fine having the event handler called just once per frame (e.g. draw a single line connecting all coalesced points). Even if hit testing every event is necessary I think rAF-aligned input offers benefits in cutting down on calls to move handlers in JS. -- GitHub Notification of comment by ChumpChief Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/278#issuecomment-466517280 using your GitHub account
Received on Friday, 22 February 2019 19:27:52 UTC