Re: [w3c/gamepad] Make getGamepads API asyncronous to support permission request (#70)

I don't think we can change `navigator.getGamepads` to be async at this point, it's implemented in multiple browsers and has been shipping for a long time. I believe most real-world usage of the API should be amenable to gating access on a permission dialog however, since the spec says that the browser should not expose devices that the user has not interacted with, so users must press a button on a gamepad in order for it to show up. The spec also describes `gamepadconnected` and `gamepaddisconnected` events that can be used in place of polling, so browsers could simply delay firing those events + exposing the gamepads in the array returned by `navigator.getGamepads()` until the user approves the permission.

However, given the spec text around not exposing devices without user interaction I would hope the fingerprinting risk here would be minimal (modulo implementation bugs). Is that not true in practice?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/70#issuecomment-393928807