[w3c/gamepad] Fast button presses could get lost (#77)

Quickly pressing/releasing buttons could get lost between calls to navigator.getGamepads()

I fully understand why the API uses a polling mechanism (and not events) to e.g. prevent 'data overflow' of analog axis events, but perhaps it could be possible to include a history on each button with timestamps and data if more than one change happened since last call to getGamepads().

This is only really an issue if the framerate drops, of course.

-- 
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/77