- From: Dave Tapuska via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2017 14:06:13 +0000
- To: public-pointer-events@w3.org
Because then you'd be in a situation whereby parent.isTrusted == false parent.getCoalescedEvents(0).isTrusted == true And you can't really determine the case whereby a person held onto coalesced events and re-dispatched them at you. isTrusted communicates whether the UA really dispatched this event or not. And if we are populating the event it should really convey the correct meaning. I'd honestly wonder if we didn't reuse the Events object and just had a dictionary of values for the coalesced events then we don't get into all this mess of saying what fields are applicable and aren't. For example why would someone think that offsetX/offsetY wouldn't work; well you'd have to read the spec that there is no target set for the event and those properties are dependent on having a target. -- GitHub Notification of comment by dtapuska Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/187#issuecomment-285359736 using your GitHub account
Received on Thursday, 9 March 2017 14:06:19 UTC