The Surface Pro 2017 is a hybrid laptop/tablet device with a detachable keyboard. The keyboard is a composite device that includes the keyboard itself, the touchpad, and possibly other sensors. Some of the collections within the composite device are incorrectly classified as gamepads by RawInputDataFetcher's heuristics.

The device names assigned by Windows for the problematic HID devices are:

\\?\HID#VEN_8086&DEV_9D3E&SUBSYS_00000000&REV_21&Col02#4&f87ce30&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
\\?\HID#VEN_8086&DEV_9D3E&SUBSYS_00000000&REV_21&Col05#4&f87ce30&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}
\\?\HID#VID_045E&PID_0922&Col06#7&36425755&0&0005#{4d1e55b2-f16f-11cf-88cb-001111000030}
\\?\HID#VID_045E&PID_0922&Col09#7&36425755&0&0008#{4d1e55b2-f16f-11cf-88cb-001111000030}

Some of the devices are shown with different IDs in html5gamepad:

"Unknown Gamepad (Vendor: 045e Product: 0951)", 2 axes, 0 buttons
"Unknown Gamepad (Vendor: 045e Product: 0951)", 2 axes, 0 buttons
"Surface Keyboard (Vendor: 045e Product: 0922)", 3 axes
"Unknown Gamepad (Vendor: 045e Product: 0922)", 2 axes, 1 button

None of these devices are usable. All axes and buttons are stuck at neutral (0.0).

This bug is particularly annoying because in some scenarios the four unusable devices occupy all four gamepad slots, meaning that actual working gamepads cannot be used until Chrome is restarted.

To fix, RawInputDataFetcher should be modified to filter out devices matching these IDs.