Re: [pointerevents] A possible immedate pointer capture processing

> I now understand the behavior that Edge (and IE11) currently has. 
Edge will immediately fire `gotpointercapture` ONLY when 
`setpointercapture' was called as a result of `pointerdown`. The code 
does NOT do anything special for `lostpointercapture` - so 
`lostpointercapture` continues to follow the spec as written. I will 
also comment on PR #76 by @NavidZ.

As I read this PR, it does not match the Edge behavior as implemented 
today.

- The changes made to section "10.1 Setting Pointer Capture" look 
good.
- The changes made to section "10.2 Releasing Pointer Capture" are not
 needed.
- I am not sure about the changes made to the "Process Pending Pointer
 Capture" paragraph. I am not sure that we need the 
`temporaryPendingPointerCaptureTargetOverride` when the 
`pendingPointerCaptureTargetOverride` seems to be sufficient.

-- 
GitHub Notification of comment by teddink
Please view or discuss this issue at 
https://github.com/w3c/pointerevents/pull/76#issuecomment-224107069 
using your GitHub account

Received on Monday, 6 June 2016 22:22:39 UTC