gamepad property on events?

While finishing up my prototype Gamepad API implementation for Gecko,
I realized that the way I've implemented something no longer makes
much sense. We've discussed exposing the set of connected gamepads on
a "navigator.gamepads[]" property (the exact location is not important
at the moment). Currently in what I've implemented, each gamepad DOM
event has a ".gamepad" property containing a DOMGamepad object with
the full state of the device. However, if there's a
navigator.gamepads, does it make more sense to instead simply have a
".index" property on the events, which indexes into
navigator.gamepads?

-Ted

Received on Wednesday, 5 October 2011 07:42:37 UTC