Re: [pointerevents] Click event while a pointer event is captured

> 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).

Even with the current spec, boundary events are not sent to other 
elements. What we're discussing removing is the boundary events that 
are sent to the captured element.

> So click is not allowed to be sent to grey if blue has capturing 
either.

But the spec says "Immediately after firing the pointerup or 
pointercancel events, a user agent must run the steps as if the 
releasePointerCapture() method has been called with an argument equal 
to the pointerId property of the pointerup or pointercancel event just
 dispatched." so even though the timing of `lostpointercapture` in 
relation to `click` is undefined, I interpret this to mean that the 
actual capturing has already ended prior to the `click` event being 
fired, even if `lostpointercapture` has not yet fired.

> 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.

I believe this is already the case, but I may have forgotten a place 
where we mention specific details about click. Is there a part of the 
spec that you think contradicts this?

-- 
GitHub Notification of comment by scottgonzalez
Please view or discuss this issue at 
https://github.com/w3c/pointerevents/issues/75#issuecomment-223477061 
using your GitHub account

Received on Friday, 3 June 2016 02:39:16 UTC