- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Jun 2016 14:45:53 +0000
- To: public-pointer-events@w3.org
There is one more thing. Edge does send a pointer move after about 3 seconds when I press mouse button and don't move at all. That causes the lostpointercapture or gotpointercapture be dispatched by that time at least once. I don't know what the origin of that synthetic event is. But Chrome or FF doesn't send that event. Do you think that might create some other compat issues that lost/gotpointercapture is delayed for an indeterminate amount on Chrome or other browsers if js sets the capture say on pointermove? I can see now the behavior of the Edge is what you say but how can we really prevent that indeterminate delay? -- GitHub Notification of comment by NavidZ Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/32#issuecomment-224303795 using your GitHub account
Received on Tuesday, 7 June 2016 14:45:55 UTC