touchstart callback doesn't work

[bvargish]

In the case below, why would mousedown work but not touchstart? I'm using createjs.Touch.enable(stage); but it doesn't make a difference. I thought maybe mousedown was overriding touchstart, but removing the mousedown listener doesn't make a difference. In my case, I want something to behave differently if a mouse is used instead of a finger.

pointsClip.addEventListener('mousedown', function(evt){
alert('mousedown');
});
pointsClip.addEventListener('touchstart', function(evt){
alert('touchstart');
});

[lannymcnie]

EaselJS objects do not actually dispatch touchStart events, but instead normalize touch events into the usual mousedown, mouseup, etc.

[bvargish]

Well that explains it! Is there a clever way to do an override with an outside class so I don't have to add code to Touch.js so it dispatches an event? My problem is that I've been asked to float a small object over a touch point by adjusting its y coordinate so it isn't obscured by a finger, but keep it locked to the cursor when using a mouse.

[gskinner]

You can look at the pointerID property. If it is -1, the event was generated from the mouse. Otherwise it is a touch.

I'm going to look into adding a isTouch property or similar to MouseEvent since this is asked frequently. Will track as a new issue.

[bvargish]

Thanks Grant! Works great on mobile devices, but unless I'm doing something wrong the pointerID property is still -1 if using a touchscreen monitor (mine's a Dell S2240T) on a computer. A more complex case I guess, especially when I see that touch doesn't work at all in Chrome like it does in Firefox, IE and Safari.

[gskinner]

@bvargish sounds like the touchscreen monitor is being treated as mouse input in the browser. The ID is set to -1 if the interaction in the browser is a mouse event, not a touch or pointer event.