New issue
Advanced search Search tips

Issue 631834 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Touch non responsive

Project Member Reported by dtapu...@chromium.org, Jul 26 2016

Issue description

Touch was not working in any tabs.

Attached is an Input Latency trace.
 
trace_chrome-touch-non-responsive.json.gz
709 KB Download
Cc: dtapu...@chromium.org
Labels: OS-Windows
Owner: ananta@chromium.org
Windows 10 laptop. Chrome stable.

ananta@ do you have a duplicate of this issue? I took a trace (was on another person's laptop).

And there was lots of touch events in the big gap in the middle. Doesn't look like we encounter any traces so I'm wondering if the touches are getting thrown out low in the stack at the hwnd handler.


Comment 2 by ananta@chromium.org, Jul 26 2016

It is possible. Is there a way I can borrow the device for testing?


Unfortunately not.
It occurred on two MS employee's laptops during our pointer events hackaton. The trace is from one of theirs.

Comment 5 by ananta@chromium.org, Jul 26 2016

it would be great if you can post the device specs here. We can try and order those 

It is a Lenovo X1 Carbon.

Touch was working and then it suddenly stopped working and wasn't working in all the tabs at the same time. Mouse continued to function.

Did you have pointer events enabled?

Comment 8 by rbyers@chromium.org, Jul 29 2016

Note that the OS was receiving the events (the Windows touch glow was visible).  They just weren't making it to Chrome somehow.

Dave, do you remember if both instances were on the X1 Carbon?  I know I spent some time trying to repro on the Surface 4 and couldn't, but it didn't reproduce easily for them either.

ananta@ I told Dave I thought I remembered you digging into some long-standing issue like this where users were occasionally reporting that no touch (or maybe it was mouse or pen) input was being processed by Chrome (but keyboard etc. still worked fine).  Sound familiar at all?

Ya they were both x1 carbon devices. They had devtools window open as a separate window. Kind of like 50/50 display but not with docking. 

Labels: Proj-TabletChrome
Owner: ----
Status: Untriaged (was: Assigned)
Unassigning all bugs for ananta@chromium.org
Cc: bokan@chromium.org
Status: WontFix (was: Untriaged)
No longer actionable and we haven't seen other bugs of this kind lately so closing.

Sign in to add a comment