Re: [pointerevents] Spec implies lost/gotpointercapture is delayed until the next pointer event but Edge does otherwise

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.

We made this change quite a while ago in response to a reported bug 
where with touch press and hold or a mouse press without mouse move, 
the `gotpointercapture` was delayed for an indeterminate amount of 
time which caused an issue for at least one site.

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

Received on Monday, 6 June 2016 22:15:09 UTC