Re: [pointerevents] Release Implicit Capture, Capture at Ancestor Element (#327)

> So for the touch case at first implicit capture goes to the child. Then when the event bubbles and parent calls setpointercapture it effectively steals the capture and after that child will not get the event (as it is not in the propagation path anymore)

Right, got that, but note I'm not even trying to steal capture - step 3 (done by the child) is relinquishing implicit capture. My understanding of the W3C docs is that that's valid.

For context, I'm a maintainer (the "events guy") for [a well-used open source project](https://github.com/openseadragon/openseadragon) that makes heavy use of pointer events (converted to "gestures") and we're getting more and more users adding overlay elements (custom implementations, other frameworks, etc) who need finer control over pointer event handling in the scenario I described. I raised the "issue" here because first, I'm not sure if I'm missing something in, or misunderstanding, the specification, and second - there seems to be many persons here that know the engines and would know if it's a bug or not.

> So if the child really doesn't care about any event they could just not have a handler

That may be the workaround I have to recommend to users, at least for now. It "feels" like a Webkit bug to me...I'll need to get my hands on some other touch devices 

Thanks much for the reply! I've followed the Pointer Events specification from the beginning... great work you guys have done, and something I've been wanting for a long time (great to see wide adoption FINALLY!)




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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 11 August 2020 22:21:15 UTC