Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 5 users
Status: Archived
Owner: ----
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug

Blocked on:
issue 175502



Sign in to add a comment
Various severe problems with touch input in Chrome for Android (scrolling, zooming, etc)
Reported by kevin.g...@gmail.com, Jun 21 2013 Back to list
Steps to reproduce the problem:
1. Load test case at http://jsil.org/tts/test
2. Pan and swipe around repeatedly to interact with the virtual joysticks

What is the expected behavior?
Once the game is loaded and running (and its touch handlers are active, see JSIL.Browser.Touch.js), touch inputs should never trigger a scroll or zoom of the document.

The game should pause sometimes in response to touch input, then resume. This is expected and the browser should handle it correctly.

Furthermore, touch input events should never get dropped or 'hang'.

What went wrong?
Swipes periodically seem to trigger scrolling operations and in some cases seem to even trigger zooming operations.

Occasionally a swipe will toggle the visibility of the Chrome address bar which resizes the document's viewport and this sometimes causes touches to get 'stuck' and remain in the game state forever (this appears to be Chrome erroneously reporting the touch in touch events, or never sending any further touch events. Not sure which)

Did this work before? N/A 

Chrome version: Chrome Beta 28.0.1500.54 1500054  Channel: beta
OS Version: 4.2.2

Note that this intentionally causes random pauses inside the touchstart/touchmove events. This is to reproduce the behavior of some unfortunate GC pauses this application used to exhibit (the GC pauses definitely made touch behavior worse).

Even without the pauses the application still does not handle touches correctly in Chrome (feel free to comment them out, they're in JSIL.Browser.Touch.js)

Of course, if you test this in desktop Chrome with emulated touch events, it works perfectly, because desktop Chrome does not ignore overflow: hidden.
 
Cc: aelias@chromium.org wiltzius@chromium.org skyos...@chromium.org klo...@chromium.org
Labels: -Cr-Content-JavaScript Cr-UI-Input-Touch-Screen
Status: Available
Comment 2 by klo...@chromium.org, Jun 24 2013
Cc: wangxianzhu@chromium.org
Can you check to see whether m27 working as expected?

We added a timeout logic in m28 for sites not responding fast for touch events. This may be the cause.
Forgive my dumb enduserness, but how do I specifically launch m27 on an android device? Just release channel?
OK, release channel Chrome on my Android 4.22 device works perfectly on that test site. No erroneous scrolls/zooms and I couldn't get the address bar to hide and 'stick' a touch either.
Blockedon: chromium:175502
Besides the timeout, this issue also depends on  bug 175502  which is about scrollability of overflow:hidden.
Comment 6 by rbyers@chromium.org, Oct 24 2013
Labels: -Cr-UI-Input-Touch-Screen Cr-Internals-Input-Touch-Screen
Project Member Comment 7 by sheriffbot@chromium.org, Mar 29 2016
Labels: Hotlist-Recharge-Cold
Status: Untriaged
This issue has been available for more than 365 days, and should be re-evaluated. Hotlist-Recharge-Cold label is added for tracking. Please re-triage this issue.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 8 by aelias@chromium.org, Mar 29 2016
Status: Archived
Sign in to add a comment