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
createjs.Touch.isSupported and a few other places use "ontouchstart" in window to check if a device is capable of using touch and which (prefixed) versions it can use.
When we tried it on a Dell Optiplex 9030, the property "ontouchstart" in window returns false in Chrome, even though that device is a touch enabled PC. If we enable the developer tools (with emulating Touch) and restart the page, Chrome returns a true there. Maybe there is a better way to
Our current workaround is setting window.ontouchstart = null; before including createjs / using createjs.Touch.enable.
If we change all occurrences of "ontouchstart" in window into (!!window.TouchEvent), we can run it on the Dell Touch PC with working touch, but we haven't tested this on a touch only / mobile device.
The text was updated successfully, but these errors were encountered:
createjs.Touch.isSupported
and a few other places use"ontouchstart" in window
to check if a device is capable of using touch and which (prefixed) versions it can use.When we tried it on a Dell Optiplex 9030, the property
"ontouchstart" in window
returnsfalse
in Chrome, even though that device is a touch enabled PC. If we enable the developer tools (with emulating Touch) and restart the page, Chrome returns atrue
there. Maybe there is a better way toOur current workaround is setting
window.ontouchstart = null;
before including createjs / usingcreatejs.Touch.enable
.If we change all occurrences of
"ontouchstart" in window
into(!!window.TouchEvent)
, we can run it on the Dell Touch PC with working touch, but we haven't tested this on a touch only / mobile device.The text was updated successfully, but these errors were encountered: