Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the hit test and capturing target for boundary events #154

Merged
merged 2 commits into from
Nov 17, 2016

Conversation

NavidZ
Copy link
Member

@NavidZ NavidZ commented Nov 8, 2016

closes #145
I followed a few suggestions mentioned in the bug.

@@ -634,7 +634,7 @@
</dd>
<dt><dfn>setPointerCapture</dfn></dt>
<dd>
<p><a href="#setting-pointer-capture">Sets</a> <a>pointer capture</a> for the pointer identified by the argument <code>pointerId</code> to the element on which this method is invoked. Subsequent events for the pointer MUST always be targeted at this element until capture is released. The pointer MUST be in its <a>active buttons state</a> for this method to be effective, otherwise it fails silently. Throws a <code>DOMException</code> with the name <code>InvalidPointerId</code> when the provided method's argument does not match any of the <a data-lt="active pointer">active pointers</a>.</p>
<p><a href="#setting-pointer-capture">Sets</a> <a>pointer capture</a> for the pointer identified by the argument <code>pointerId</code> to the element on which this method is invoked. For subsequent events of the pointer, capturing target will substitute the normal hit testing result as if the pointer is always over the capturing target and they MUST always be targeted at this element until capture is released. The pointer MUST be in its <a>active buttons state</a> for this method to be effective, otherwise it fails silently. Throws a <code>DOMException</code> with the name <code>InvalidPointerId</code> when the provided method's argument does not match any of the <a data-lt="active pointer">active pointers</a>.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest a slight rewording: "For subsequent events of the pointer, the capturing target will substitute the normal hit testing result...target, and they MUST always.." (note the added comma after "target" too)

@patrickhlauke
Copy link
Member

LGTM barring the slight tweaks to the last changed sentence.

@NavidZ
Copy link
Member Author

NavidZ commented Nov 16, 2016

Any other comments on this this? Is it okay to land this?

@teddink
Copy link

teddink commented Nov 16, 2016

Looks good - I reviewed this with development last week,

@RByers
Copy link
Contributor

RByers commented Nov 17, 2016

LGTM

@RByers RByers merged commit 91b6608 into w3c:gh-pages Nov 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Need to clarify what triggers boundary events when releasing a capture
4 participants