On 12/6/2013, 12:00 PM, Ehsan Akhgari wrote:
On 12/6/2013, 11:43 AM, Ted Mielczarek wrote:
On 12/6/2013 11:33 AM, Ehsan Akhgari wrote:
Thanks for posting this, Ted!
What is the dom.gamepad.non_standard_events.enabled controlling, and
why do we have a different value of this pref in our release
On 12/6/2013, 11:43 AM, Ted Mielczarek wrote:
On 12/6/2013 11:33 AM, Ehsan Akhgari wrote:
Thanks for posting this, Ted!
What is the dom.gamepad.non_standard_events.enabled controlling, and
why do we have a different value of this pref in our release and
non-release builds?
That pref controls
On 12/6/2013 11:33 AM, Ehsan Akhgari wrote:
> Thanks for posting this, Ted!
>
> What is the dom.gamepad.non_standard_events.enabled controlling, and
> why do we have a different value of this pref in our release and
> non-release builds?
>
That pref controls whether we send "gamepadbutton{up,down}
Thanks for posting this, Ted!
What is the dom.gamepad.non_standard_events.enabled controlling, and why
do we have a different value of this pref in our release and non-release
builds?
Thanks!
Ehsan
On 12/6/2013, 7:47 AM, Ted Mielczarek wrote:
As of Firefox 28 I intend to turn the Gamepad AP
As of Firefox 28 I intend to turn the Gamepad API on by default (on
desktop Firefox). It has been developed behind the dom.gamepad.enabled
preference, and shipped preffed-off in Firefox 24.
Google has shipped a prefixed but mostly-compatible implementation in
Chrome for multiple releases now. The
5 matches
Mail list logo