- From: C. Van Wiemeersch <notifications@github.com>
- Date: Tue, 28 Nov 2017 14:43:14 +0000 (UTC)
- To: w3c/gamepad <gamepad@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 28 November 2017 14:43:41 UTC
if we’re looking to make the Gamepad API safe for DOM contexts (which other issues cover), it probably makes sense to start thinking of creating a `navigator.gamepads` namespace. similar thing happened for `navigator.getUserMedia` to `navigator.mediaDevices.getUserMedia` and `navigator.getVRDisplays` to `navigator.vr.requestDevice`. this might warrant its own issue, but this is all could be handled by namespacing the API, moving the DOM events to emit on an `EventTarget` interface, and creating a Promise-based `navigator.gamepads.get(…)` thoughts? -- 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/23#issuecomment-347544761
Received on Tuesday, 28 November 2017 14:43:41 UTC