Re: [w3c/gamepad] Should spec a buffering/refresh interval model of gamepad data? (#22)

> In chromium [...] We poll gampads from the OS at 60Hz and we produce a snapshot of the actual state - as provided by the OS, which might already include some buffering and/or delay - which is returned in getGamepads().

Just for posterity, this is not true anymore, see https://github.com/w3c/gamepad/issues/46#issuecomment-898047035

> Chrome currently polls at 250 Hz (4ms polling interval):
> 
> https://source.chromium.org/chromium/chromium/src/+/main:device/gamepad/gamepad_provider.cc;l=100;drc=d024ced704c7a375bce2d9d6654ae4807bfe934b

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

Message ID: <w3c/gamepad/issues/22/2350903738@github.com>