- From: Dave Tapuska via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2017 14:21:46 +0000
- To: public-pointer-events@w3.org
On the converse of my point... I could do something like:
var a = event.getCoalescedEvent(0);
foo.dispatchEvent(event);
console.log("isTrusted " + a.isTrusted);
It is odd that the isTrusted changes even though you didn't do something to the child object itself. That is why I had a discussion with Navid about whether we just say isTrusted is bogus like the rest of the fields we said were bogus, target, relatedTarget, bubbles, stopPropogation, etc...
But to me this feels like a wart we are adding to the web platform possibly.
@RByers any opinion?
I know we did think that if someone wanted to change their code from using the "unioned" events to using the coalescedEvents then they'd just add a for loop and that was the thought around using Events but I don't know if that makes a whole lot of sense anymore.
--
GitHub Notification of comment by dtapuska
Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/187#issuecomment-285363719 using your GitHub account
Received on Thursday, 9 March 2017 14:21:53 UTC