- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Sep 2021 21:19:40 +0000
- To: public-pointer-events@w3.org
I don't know what @jakearchibald meant by "the event was created by the browser". 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. Otherwise this logic of `if event.getCoaelscedEvents() is empty then use event` will lurk into all codes. I have a vague memory that it was called out somewhere in the spec but I don't seem to find it now as @mustaqahmed mentioned. Maybe it even never was there and it was always in my head. But this approach is visible in [the example](https://www.w3.org/TR/pointerevents/upcoming/#:~:text=the%20order%20of%20all%20these%20dispatched%20events%20should%20) I added back then in the spec that mentions the coalesced events count. -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/409#issuecomment-914636938 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 September 2021 21:19:42 UTC