Re: [pointerevents] Set coalesced events isTrusted flag to false

I don't have a strong opinion on the bigger picture question of whether it's better to use `Event` instances or dictionaries with a subset of the properties - they each have their tradeoffs.  We discussed it at TPAC and I believe @smaug---- said he preferred Events which is why we chose that.  And I know this shouldn't really matter relative to the other concerns, but I don't think any of us really wanted to have to maintain duplicate definitions in the spec including for properties defined in other specs (`clientX` etc). 

IMHO it's not really worth re-litigating that decision now. The `getCoalescedEvents` API is already a relatively niche use case, I think it's unlikely that these details we're worried about are going to impact any developer in practice.

IMHO we don't get much real benefit in practice by clearing the `isTrusted` bit on dispatch (the only real protection against abuse is in extension scenarios, since there's no protecting against malicious code running in the same context).  I'd personally just go with @smaug----'s suggestion of propagating `isTrusted` from the parent event, and not worrying about trying to clear it on re-dispatch.  Developers already need to be thoughtful about where an Event object is coming from when making important decisions based on `isTrusted`, this is just one more case (which IMHO is extremely unlikely to matter in practice).

GitHub Notification of comment by RByers
Please view or discuss this issue at using your GitHub account

Received on Thursday, 9 March 2017 14:33:49 UTC