| commit | 0bca9e9579ee5405f61eeb4eaafd125d19304c13 | |
| author | ananta <ananta@chromium.org> | |
| Tue, 3 Mar 2015 23:20:47 +0000 (3 15:20 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Tue, 3 Mar 2015 23:22:01 +0000 (3 23:22 +0000) | ||
| tree | b9c5961c5a696823abdd91eaa1b523559f56a951 | treesnapshot (tar.gz zip) |
| parent | 5b90c6fdbd3097080752fcf15f2f0e5ae4d3aec3 | commitdiff |
Ensure that the on screen keyboard detection on Windows 8+ is more reliable.
The keyboard detection code is heuristic based as we don't have a reliable way to detect if a keyboard
is attached. We use the Setup API's for keyboard class GUID's and look for specific prefixes in the device names like
ACPI\PNP*, ACPI\MSF* and HID\VID*. If we find one of these we assume that a keyboard is present.
Fixed a bug in the keyboard detection function where in the order of params for the StartsWith helper was flipped.
This works on the Surface and Samsung touch screen laptops in my testing.
BUG=335735
Review URL: https://codereview.chromium.org/969293002
Cr-Commit-Position: refs/heads/master@{#318961}
The keyboard detection code is heuristic based as we don't have a reliable way to detect if a keyboard
is attached. We use the Setup API's for keyboard class GUID's and look for specific prefixes in the device names like
ACPI\PNP*, ACPI\MSF* and HID\VID*. If we find one of these we assume that a keyboard is present.
Fixed a bug in the keyboard detection function where in the order of params for the StartsWith helper was flipped.
This works on the Surface and Samsung touch screen laptops in my testing.
BUG=335735
Review URL: https://codereview.chromium.org/969293002
Cr-Commit-Position: refs/heads/master@{#318961}
| base/win/win_util.cc | diffblobblamehistory |