Open jcf120 opened 7 years ago
Not sure I'd call it a "bug" more an attribute of IE's touch implementation.
From what I hear Microsoft have been keen to "optimise" touchmove style events by not firing them unless you remove the possibility user agent needing to do anything. This carries through to the now standardised pointers I've event. In all, one more reason why I'm not a big fan of Microsoft anymore.
So basically the options to get these events to fire will have bad side effects on the element no matter what we do and because the effects aren't easily testable we'll have to apply a performance effecting fix to everything to be predictable.
Comes back down to if having touch gestures enabled should automatically disable the default action. I'd argue just not to support IE mobile given the depth of the change, particularly as it's a dying platform. Doesn't solve pointerevents in general but the touch events API won't be depreciated any time soon
On 6 Mar 2017 10:33 am, "jcf120" notifications@github.com wrote:
Seems Doom is victim to this bug: http://stackoverflow.com/questions/25620397/pointermove-does-not-fire-for- touch-on-ie
The touch-action: none hack works, but causes other issues. Any thoughts?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/shortercode/Doom.js/issues/24, or mute the thread https://github.com/notifications/unsubscribe-auth/AIoe2dLtN230r8TF2OdIdM8tMUMLxiliks5ri-EIgaJpZM4MT-W3 .
Seems Doom is victim to this bug: http://stackoverflow.com/questions/25620397/pointermove-does-not-fire-for-touch-on-ie
The
touch-action: none
hack works, but causes other issues. Any thoughts?