UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Open the attached file with an calibrated joystick plugged in
2. Observe that the recorded readings match the uncalibrated ones, the ranges reported by chromium range from -0.96 to 0.3, with the middle point on -0.3
3. 

What is the expected behavior?
I expect chromium to follow any gamepad calibration configured into windows, reporting, as the GamePad API requires, values mapped to a range between -1.0 to 1.0 with the middle point on 0.0

What went wrong?
Instead of following the correct -1.0 to 1.0 mapped values as reported as after the windows calibration, but instead it reports the -0.96 to 0.3 values as windows received it before it got calibrated

Did this work before? No 

Does this work in other browsers? No
 Edge: No gamepad api support
Firefox: Also ignores Windows calibration

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version: 

Windows has 2 options for getting the range of game controller axis, raw and non raw, for most implementations the raw versions are better suited, but they completely bypass the windows calibration settings, and this isn't noticed by many developers, as most never devices come properly "hardware" calibrated, instead of requiring "software" calibration.
 

Deleted: gamepad.html 983 bytes

gamepad.html 983 bytes View Download