W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: PSA: publishing new WD of Gamepad on April 14

From: Ted Mielczarek <tmielczarek@mozilla.com>
Date: Mon, 13 Apr 2015 09:04:26 -0400
Message-ID: <CACL_6fSEvz+72yN5qR=xr9n7-7swLW-Bwi_h+2Tm76tUGZpK3A@mail.gmail.com>
To: Ashley Gullen <ashley@scirra.com>
Cc: Arthur Barstow <art.barstow@gmail.com>, public-webapps <public-webapps@w3.org>
On Thu, Apr 9, 2015 at 5:15 PM, Ashley Gullen <ashley@scirra.com> wrote:

> Why doesn't the Gamepad API fire events for button pushes or axis
> movements? For example when pressing a mouse button or moving the mouse the
> browser fires "mousedown" and "mousemove". The Gamepad API however requires
> you to passively poll the state regularly (probably in rAF) and look for
> changes yourself. Why does it not fire events like "gamepadbuttondown" or
> "gamepadaxischange"? This would have a few advantages:

Hi Ashley,

We've talked about this at length, and Firefox even includes a prototype
implementation of button and axismove events (about:config, search for
dom.gamepad.non_standard_events.enabled), but I just don't have the time to
spec them out usefully right now and I'd like to finish up spec'ing the
already-interoperably-implemented set of stuff that's in the spec right
now. Once we get that out the door we can work on useful additions like
events. There's a wiki page[2] that already has a list of such useful


2. https://www.w3.org/wiki/Webapps/GamepadFeatures
Received on Monday, 13 April 2015 13:04:55 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC