Re: [w3c/gamepad] spec `gamepadbuttondown` and `gamepadbuttonup` events (issue #4) (#15) from C. Van Wiemeersch on 2018-10-22 (public-webapps-github@w3.org from October 2018)

From: C. Van Wiemeersch <notifications@github.com>
Date: Mon, 22 Oct 2018 21:21:22 +0000 (UTC)
To: w3c/gamepad <gamepad@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/gamepad/pull/15/c431991695@github.com>

> Is this still a thing that's going to be added to the spec?

I think there's still interest from web developers in having an event model for button changes (or an improved API for polling).

related: see @nondebug's comment here: https://github.com/w3c/gamepad/issues/83#issuecomment-413636028


also see these various issues around polling:

#77 – Fast button presses could get lost
#46 – Arbitrary buffering of API calls is causing issues
#22 – Should spec a buffering/refresh interval model of gamepad data?
#8 – Need to spec liveness of Gamepad objects
#4 – Should fire events instead of using passive model

-- 
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/pull/15#issuecomment-431991695

Received on Monday, 22 October 2018 21:21:45 UTC