- From: Patrick H. Lauke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Apr 2016 13:39:34 +0000
- To: public-touchevents@w3.org
(just edited the previous comment, as further testing reveals there's some reason behind the strange behavior of Chrome and Firefox on Android - it's not that a new touch is added to index 0, but rather it seems that if a touch is removed and then a new touch is added, this new touch is given the index of the previously removed one...like it has some sort of "memory") -- GitHub Notification of comment by patrickhlauke Please view or discuss this issue at https://github.com/w3c/touch-events/issues/13#issuecomment-205809046 using your GitHub account
Received on Tuesday, 5 April 2016 13:39:36 UTC