- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Jun 2016 02:25:42 +0000
- To: public-pointer-events@w3.org
I modified the original issue to have the outputs right after each scenario to make it more clear. So basically in 3, what I'm saying is that if click is defined as an event that will be fired to the first common ancestor of pointerdown and pointerup targets then scenario 4 makes sense. However from my understanding of the current spec no event should be fired to an element that doesn't have capturing except the boundary events (which we are trying to remove that to in other issues anyway). So click is not allowed to be sent to grey if blue has capturing either. Solution 3 of mine suggests to just explicitly exclude click from this in the spec and let click always be sent to the first common ancestor of pointerdown/up targets as per definition. -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/75#issuecomment-223475520 using your GitHub account
Received on Friday, 3 June 2016 02:25:47 UTC