You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that in some cases it was possible to create a "pinch" gesture in IE11 on the destkop even though I was only using the mouse. Looking deeper, it turns out that when I dragged an image IE fired the mousedown event but not the mouseup event. If I did it again, hammerjs registered that as two separate pointers and started firing the pinch event. Example here:
I'm using Windows 7 IE 11. I'm guessing it's broken on any IE that supports pointer events. To duplicate, click and drag the image so that you get the ghost image effect. Let go of the image. Then do it again and you will see pinch events fired.
I've created a fix locally and I'm working on a PR now.
The text was updated successfully, but these errors were encountered:
jbrantly
added a commit
to jbrantly/hammer.js
that referenced
this issue
Sep 11, 2014
It is possible for IE to fire a "down" event without a corresponding "up"
event. If this happens, a new "down" event will be falsely added as an
additional pointer. This commit first makes sure the pointer from the
down event is not already in the store before adding it (based on
pointerId).
Fixeshammerjs#664
I noticed that in some cases it was possible to create a "pinch" gesture in IE11 on the destkop even though I was only using the mouse. Looking deeper, it turns out that when I dragged an image IE fired the mousedown event but not the mouseup event. If I did it again, hammerjs registered that as two separate pointers and started firing the pinch event. Example here:
http://jsfiddle.net/jbrantly/410zu0wn/
I'm using Windows 7 IE 11. I'm guessing it's broken on any IE that supports pointer events. To duplicate, click and drag the image so that you get the ghost image effect. Let go of the image. Then do it again and you will see pinch events fired.
I've created a fix locally and I'm working on a PR now.
The text was updated successfully, but these errors were encountered: