- From: Dave Tapuska via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Feb 2019 19:44:26 +0000
- To: public-pointer-events@w3.org
I believe spec text Navid wrote is `Note that this rule doesn't apply to target and it should still be the same as the dispatched event's target.` So all coalesced events will have the same target. Each coalesced event doesn't have its target calculated it is just cloned from the parent event. Yes you will still have the coalesced event problem even in the raw events scenario, so it further goes to the point that having the `pointerout/over/enter/leave` as discrete events doesn't fix the issue. I guess what you really want is a `really raw` event where every coalesced event ends up as a true JS event. Are there practical applications that this is causing issues for. A lot of the web might use event delegation and this wouldn't even apply to. Secondly we expected apps that are using coalesced events to be drawing apps and their targets would largely be a large canvas. Just trying to get my head around a concrete example. -- GitHub Notification of comment by dtapuska Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/278#issuecomment-466522662 using your GitHub account
Received on Friday, 22 February 2019 19:44:28 UTC