- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Sep 2021 09:25:08 +0000
- To: public-pointer-events@w3.org
@NavidZ > I don't know what @jakearchibald meant by "the event was created by the browser". Developers can call `new PointerEvent(…)` and pass in their own values. I'm talking about trusted `PointerEvent`s created by the browser in response to a pointer move. > But if we were to stick with the idealogy of devs should either work purely with the dispatched `event`s alone or with the `event.getCoaelscedEvents()` then an event should always have a coalesced event. Agreed. > Otherwise this logic of `if event.getCoaelscedEvents() is empty then use event` will lurk into all codes. That's what I had to add https://github.com/GoogleChromeLabs/pointer-tracker/commit/434a8ec8ffbd19d02a5fde0871bce28008ac8914#diff-d5a4b3a0309f2337144861084c1014523cced561eb722cb9684c63f5e41e0567R52. I think the spec needs an algorithm for "reacting to a pointer update", which details how values are updated and events are dispatched. This would include updating the coalesced event list, flushing deferred events, hit testing, targeting etc etc. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/409#issuecomment-915070438 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 September 2021 09:25:09 UTC