New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 779022 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

touchcancel is not emitted for all canceled touches

Reported by geop...@gmail.com, Oct 27 2017

Issue description

Steps to reproduce the problem:
The attached page uses an ES6 Set to track all active touches; when a touchstart is received, it adds the touch(es) to the set, when a touchend or touchcancel is received, it removes the touch(es) from the set.

To reproduce the problem:
1. Open the attached page on Chrome on Android.
2. Touch and hold 2 fingers anywhere in the page. You should see the ids of the 2 touches reported at the top of the page.
3. While holding the touches, tap on the tab number button next to the location bar (in the browser ui) to switch to the preview of all browser tabs. This should cancel all active touches in the page.
4. If you go back to the tab, one of the touches will still be shown as active.

What is the expected behavior?

What went wrong?
When something happens that should cause all touches to be canceled, only one touchcancel event is emitted and it contains only one Touch in changedTouches.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 61.0.3163.98  Channel: n/a
OS Version: 5.1
Flash Version:
 
index.html
1.5 KB View Download
Labels: Needs-triage-Mobile
Cc: nyerramilli@chromium.org sandeepkumars@chromium.org
Components: Internals>Input>Touch>Screen
Labels: Triaged-Mobile Needs-Feedback
Tested the issue in Android, somehow I could not reproduce the issue.

Steps Followed: 
1. Launched Browser
2. Opened above file in a tab
3. Tap and hold 2 fingers, observed 2 numbers triggered
4. Tried tapping on tab switcher with other finger
5. Observed both the numbers got disappeared on going back to the tab 

Chrome versions tested:
61.0.3163.98

OS
Android 5.0.0

Android Devices
5.0.0:; Micromax A106 Build?LRX21M

@geopoul: Could you please find the above steps and help us with the details of your device and screencast for further triaging of the issue.

Thanks!!

Comment 3 by geop...@gmail.com, Nov 2 2017

I recorded a video of my cell phone to show my exact actions that trigger this problem. I am using a cheap Chinese phone running Android 5.1 / Chrome 61.0.3163.98. I've also tried this on a Huawei Nexus 6P (running Android 8.0.0 / Chrome 61.0.3163.98) and I got identical results.

Comment 4 by geop...@gmail.com, Nov 2 2017

vid.mp4
421 KB View Download
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 2 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: M-64
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue in Android. Observed touch event is seen

Steps Followed: 
1. Launched Browser
2. Opened above file in a tab
3. Tap and hold 2 fingers, observed 2 numbers triggered
4. Tried tapping on tab switcher with other finger
5. Observed Observed touch event is seen

Chrome versions tested:
61.0.3163.98, 64.0.3256.0

OS
Android 8.0.0

Android Devices
8.0.0 Nexus 5X Build/OPR1. 170623.030

This seems to be a Non-Regression issue as same behavior is seen since M55, Untriaged for further input's on this

Please navigate to below link for log's and video--
go/chrome-androidlogs/779022

Thanks!!

Cc: nzolghadr@chromium.org
Components: -Internals>Input>Touch>Screen Blink>Input
Still reproduces in Android M69. Input team seems like a good first step; we seem to fire one touchcancel when the tab-switcher button is pressed but not both?
Status: Available (was: Untriaged)
Here's a real life example of how this bug affects the mobile website of Google Maps.

If you look at the video, initially everything works just fine: you can pan the map using using one finger and you can zoom in/out using two fingers. But if you tap on the tab switcher while two fingers are touching the page, then one of the two touches gets stuck. So if you go back to the tab, touching the map with one finger will cause it zoom in/out. (If you touch it with two fingers it will reset the stuck touch and everything will go back to normal).

Sign in to add a comment