1058497 - Gamepad API only works after removing and restoring Focus in Firefox 34

Status: RESOLVED INCOMPLETE

(Core :: DOM: Events, defect)

Description

[jonas echterhoff]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10) AppleWebKit/538.46 (KHTML, like Gecko) Version/8.0 Safari/538.46

Steps to reproduce:

1. Attach a gamepad.
2. Run Firefox Nightly on OS X, and go to http://files.unity3d.com/jonas/gamepadTest/ (sorry development build with large build size)
3. Press buttons on the gamepad
4. Notice nothing happens
5. Un-focus the page (by pressing on the URL bar), and refocus it
6. Press buttons on the gamepad again.
7. The page should start listing the gamepad and inputs from the gamepad


Actual results:

The gamepad was only detected by unfocusing and refocusing the page, in step 7. above.


Expected results:

The gamepad should have been detected as soon as buttons are pressed, in step 4. above. This is the behavior in Firefox 29.

Comment 1

[Loic]

Jonas, as it worked in FF29, could you install the tool mozregression to find a possible regression range, please.
See http://mozilla.github.io/mozregression/ for more details.

NB: I don't have any gamepad to test, but is it possible to mimic a gamepad in Firefox?

Comment 2

[(not currently active) Ted Mielczarek]

Simpler test page, FWIW:
http://luser.github.io/gamepadtest/

I can't reproduce with the simple test page on OS X 10.9.4 with today's Nightly. I tried 3 different controllers including a DualShock 4, and I also tried with a fresh profile. It might be something specific to the way Unity is using the API? I'll try reproducing with your testcase next (my home internet is slow).

Comment 3

[(not currently active) Ted Mielczarek]

Your demo from comment 0 works for me with today's Nightly. What kind of gamepad are you using, and are you actually on OS X 10.10 as your user agent suggests?

Comment 4

[jonas echterhoff]

Hmm, this seems to be a bit more specific to my setup. I tried the mozregression tool, but could not reproduce it on any revision in that. So, next, I tried running Firefox with a clean profile, and could not reproduce it either, so it has to be specific to my setup (which, I guess, makes it much less severe). More findings:

-http://luser.github.io/gamepadtest/ (or any of the other public gamepad API test pages) works fine. So it has to be specific to something we do indeed.

-Yes, I am on OS X 10.10

-My GamePad is an old MacAlley iShock II (probably very uncommon these days) - which, btw, does not show all axes in Firefox (it does in Chrome, though), but given how uncommon that pad is, I did not file a bug on that.

So, not sure how to proceed - given that this seems to be specific to my setup, are there any settings i should look at?

Comment 5

[(no longer active)]

Hey guys, this is an example of a bug where it would be nice to get a regression range.

Comment 6

[u279076]

(In reply to :Ehsan Akhgari (not reading bugmail, needinfo? me!) from comment #5)
> Hey guys, this is an example of a bug where it would be nice to get a
> regression range.

Sure, I'll see what I can come up with.

Comment 7

[u279076]

Re-flagging myself so I don't lose this.

Comment 8

[Ada [:adalucinet]]

Couldn't reproduce this issue on Nightly 37.0a1 (Build ID: 20150109030224) with both Xbox 360 controller and Logitech Gamepad F310 on Mac OS X 10.10 nor 10.9.5. Although, found 2 different issues:
1. On latest Nightly with e10s enabled, controllers are not working with both test pages from comment 0 and comment 2. Ted, do you have any idea why?
2. Crash bug 1119805.

Comment 9

[(not currently active) Ted Mielczarek]

Alexandra: Gamepad is currently stubbed out in e10s, that's bug 852944. (Unfortunate now that e10s is on by default on Nightly.)

Comment 10

[u279076]

I've been trying to track down a MacAlly iShock II and finally found one on EBay. Once I get it in the office I'll see if I can reproduce this. Sorry it's taking so long.

Comment 11

[u279076]

I finally got the gamepad delivered today and tested this but was unable to reproduce the bug as described. Both the test page in comment 2 and comment 0 work as expected. My game controller is detected as "2222-4020-Macally iShock II FFB Game Controller" and all buttons register a response on the test pages. I tested this with the latest Firefox Nightly build.

Jonas, can you please confirm this is an issue for you with the latest Nightly build:
https://nightly.mozilla.org

Comment 12

[u279076]

I am resolving this bug as incomplete due to a lack of response and information to move this report forward. Please reopen this bug report if you have new information about reproducing this bug in the latest Nightly.