- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 May 2019 15:55:53 +0000
- To: public-pointer-events@w3.org
@annevk what do you mean the memory of the event path? This all is more or less explained in this draft as well. But just to reiterate. They will have the coordinates of the event path and they go back to the last event that was dispatched to js. So for example if js is keeping the main thread busy they wouldn't receive any event until they are done running the js code. Then they will get one move event and all the other move events that have happened during this busy time as coalesced events of that dispatched event. Note that the coalesced events aren't hit-tested by themselves (maybe this is the confusion). So it is not like that they will have their own targets. They just return the same target as the dispatched event. So when the dispatched target is protected against shadow DOM through normal dispatching algorithms steps these coalesced events will get that protection automatically. Is that more clear? -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/pull/280#issuecomment-493505401 using your GitHub account
Received on Friday, 17 May 2019 15:55:54 UTC