- From: mingchou via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Aug 2016 08:42:18 +0000
- To: public-pointer-events@w3.org
mingchou has just created a new issue for https://github.com/w3c/pointerevents: == What is the relationship between setPointerCapture, PointerLock, and browser default behaviors? == [Here](http://jsbin.com/masuya/2/edit?html,output) is the first test. It setPointerCapture to another element when mousedown on a input element with type=range. setPointerCapture works on Chrome Canary and the slider doesn't move. But the behavior is strange after pointerup and releasePointerCapture. Edge handles it as setPointerCapture doesn't be called. [This](http://jsbin.com/giqopi/edit?html,output) is the second test of setPointerCapture with dnd. setPointerCapture works until dragstart. The difference between Edge and Canady is that Edge fires lostpointercapture after dragstart while Canary fire lostpointercapture when releasing mouse button. [This](http://jsbin.com/huyocu/edit?html,output) is the third test. When you selected the text and drag it, setPointerCapture will not capture pointers after dragstart. [This](http://jsbin.com/zasesu/edit?html,output) is the fourth test. One element setPointerCapture and the other requestPointerLock. Please ignore this case if it will be covered by [issue#131](https://github.com/w3c/pointerevents/issues/131). On Canary, requestPointerLock works but setPointerCapture not. On Edge, the result is opposite. My question is will we define the relationships between browser default behaviors, dnd, pointerlock, and setPointerCapture? Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/135 using your GitHub account
Received on Thursday, 25 August 2016 08:42:25 UTC