Speculative fix for MaxTouchPoints returning incorrect value on Windows.
commitc7c9e396975f37ef865bf4cea63ac64d93295a3d
authorbokan <bokan@chromium.org>
Thu, 11 Sep 2014 21:07:40 +0000 (11 14:07 -0700)
committerCommit bot <commit-bot@chromium.org>
Thu, 11 Sep 2014 21:27:39 +0000 (11 21:27 +0000)
tree0356e1ed682394a9223d4ea6cfdb2c163cab0f2f
parent043f36003d1d0a36be39f7eb071eeab5970d6300
Speculative fix for MaxTouchPoints returning incorrect value on Windows.

Windows 7 appears to sometimes return an incorrect value for max touch
points, returning 1 when there's in fact no touch devices present. This
breaks some web pages that use a non-zero number of touch points as a
signal that the devices has a touch screen. As this is specific to certain
Win7 configurations, I don't have a repro; however, reports in the bug
show that the SM_DIGITIZER setting does indeed return the correct status
of "no touchscreen". In light of this, we speculatively return 0 touches
if there's no touchscreen device present.

BUG=352942

Review URL: https://codereview.chromium.org/563853002

Cr-Commit-Position: refs/heads/master@{#294467}
ui/base/touch/touch_device_win.cc