New issue
Advanced search Search tips

Issue 811273 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-08-20
OS: Windows
Pri: 3
Type: Task



Sign in to add a comment

Remove workaround for missed touch-end events

Project Member Reported by girard@chromium.org, Feb 12 2018

Issue description

Some win7-vintage touch drivers occasionally fail to send touch-end events. We suspect the failures happen when multiple touches happen at the same time (via mashing your hand and fingers into the screen.)

Although touch-end events don't fire, the drivers do accurately report the number of active touches. Thus our workaround watches for touches that disappear from the active touch list without sending a corresponding touch-end. When we detect that we generate a simulated touch-end.

There is an UMA stat (TouchScreen.MissedTOUCHEVENTF_UP) that tracks the number of times that the workaround fires. We should track that stat and watch for diminished usage - this would indicate that users are no longer using Win7, and that this workaround is no longer needed.

Note: In this bug, the term "driver" should map to the hardware driver + the OS support in Win7. It's unclear where in that stack the failure happens.

We've seen this in Dell Optiplex AIO 9020 and 7010 (touch versions) and Lenovo Horizon (tabletop)

See  issue 792892  and issue 316085 for more discussion.
 

Comment 1 by sadrul@chromium.org, Feb 20 2018

Cc: sadrul@chromium.org
NextAction: 2018-08-20
Setting a next-action date in 6 months.
The NextAction date has arrived: 2018-08-20
Cc: lanwei@chromium.org
Owner: nzolghadr@chromium.org
Status: Assigned (was: Available)
--> nzolghadr@ for triage. /cc+ lanwei@ fyi
Do we have a way of reproducing this locally reliably or is it happening only in the wild?
I am not sure, but looking at the UMA data [1], it looks like the usage is going down over time, but very slowly (~19K reports in May, ~16K reports in Aug).

[1] https://uma.googleplex.com/p/chrome/timeline_v2/?sid=c984822025c694b80173cdd64ee75ac2

That's 16K users filing about 100K events. Note that UMA only tracks opted-in users, so the number of affected users will be larger.


Sign in to add a comment