New issue
Advanced search Search tips

Issue 740084 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Scrolling stuck / touch input events not handled on android chrome

Project Member Reported by eseckler@chromium.org, Jul 7 2017

Issue description

Chrome Version: 61.0.3142.0 (dev)
OS: android

Don't have a reliable repro, here's what I did:
(1) Browse (load web page).
(2) Scroll page.
(3) Lock phone.
(4) Unlock phone.

Tab scroll position got stuck - cannot longer use touch/drag on phone to scroll the page. Tried a few things to try and get it unstuck without success:
- opening a new tab
- closing another tab
- opening menu, settings
- opening chrome home

I was able to inspect the tab remotely via devtools and scroll remotely (click&move in inspector). Still, even after that, I can't scroll on phone.

Captured traces for the problem as well, one with standard categories, one with all categories, see attachments. It looks like input events are received in browser, but not forwarded.

cc-ing jinsukkim@ who seems to have authored the code that deals with receiving the touch events in Java (GestureProvider::OnTouchEvent is what pops up in the trace) and might be able to direct this to someone with the relevant domain knowledge.

 
trace_no_scroll.json
1011 KB View Download
trace_no_scroll_all_categories.json
6.6 MB View Download
Does this look related? Issue 739807 I happen to be this week's stability sheriff, and I'm waiting for sahel@'s feedback before I start blaming myself : )
I didn't see anything crashing in this case, but could be related to the patch you're suspecting there. Dunno :)
Owner: jinsuk...@chromium.org
Status: Available (was: Untriaged)
Both start showing up from 61.0.3142.0, which leads me to pointing the finger to others first. Assigning to myself but I'll keep monitoring Issue 739807 for now.
Cc: eseckler@chromium.org
 Issue 736623  was fixed. Let me know if the issue is still reproducible. That would tell us if they are related.
This may have been a duplicate of  Issue 747733  which got fixed by now. Let me close this. Feel free to reopen it if it happens again.
Status: WontFix (was: Available)

Sign in to add a comment