ngTouch event coordinates should not report incorrect values

[MrHash]

ClientX and ClientY click event values are not reported correctly on device browsers e.g. iOS6/Android, but works correctly on desktop browsers.

Please see demonstration http://plnkr.co/edit/9mSIhXrSbehfkirx359U?p=preview and test on mobile Safari/Chrome. Clicking inside the element returns incorrect values while clicking outside returns correct results.

This most likely covers the problem raised in issue #4428.

[tbosch]

Right, we are using the touchstart event and forwarding it to the click handlers. However, touch events don't have clientX and clientY properties on the event but on the modified touches that are stored on the event.

[MrHash]

OK the coords do seem to be available at event.changedTouches[0]. Is this the correct way to reference or does this remain a bug?

[tbosch]

Yes, this is the correct way, see https://developer.mozilla.org/en-US/docs/Web/API/TouchEvent.changedTouches.

Actually, if you have two fingers down, you may want to have the coordinates of both of them in your event handler.
So keeping this under event.changedTouches makes sense!

Closing this as not an issue then!