- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Thu, 18 Aug 2016 01:47:25 +0000
- To: public-pointer-events@w3.org
You understanding is correct regarding postponing got/lostpointercapture and immediately taking effect in hasPointerCapture. As you can see in [this section](https://w3c.github.io/pointerevents/#dom-element-haspointercapture) "hasPointerCapture" returns true or false only based on pendingPointerCaptureTarget which immediately gets updates as the result of call to setPointerCapture and releasePointerCapture. So the return value of the function immediately takes effect when calling set/releasePointerCapture. But whether an element received got/lostpointercapture is a delayed notion defined in [process pending point](url) and will be processed before the next pointerevent. If you are confused with why hasPointerCapture is defined in a way that takes effect immediately as oppose to the got/lostpointercapture delayed model maybe it helps to read the related issue #121 . There are some justifications for this behavior. -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/133#issuecomment-240601299 using your GitHub account
Received on Thursday, 18 August 2016 01:47:32 UTC