Re: [w3c/gamepad] Arbitrary buffering of API calls is causing issues (#46)

I'm not really sure how we solve this with XInput, to be honest, since it doesn't provide a notification API. I don't think any browser is going to make `getGamepads()` call directly into XInput, since it's likely to be executing in a sandboxed content process. For other sources of input we generally get notified on new data, so adding events to the spec would fix this use case.

-- 
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/46#issuecomment-258127780