Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

Gamepad api doesn't work in firefox but it does in chrome

  • 2 odpowiedzi
  • 0 osób ma ten problem
  • 1 wyświetlenie
  • Ostatnia odpowiedź od zeroknight

bendca61
bendca61
more options

I am using the web api for videogame controllers to make a web remote controller for a robot, i use django to host the server. When i access the ip of the Django server in firefox i get errors like: getGamepads is not a function or errors while trying to get gamepads from the navigator, but when i access through chrome this does not happen. These errors only happen while accessing through the django server, when i access through the local file or other pages in the web that use gamepad api there is no issue. Because of that i think that it has something to do with firefox tight security restrictions on http sites, but i can't find a way to grant permission to my page to work properly, i am willing to compromise in security since it's just going to be used locally

I am using the web api for videogame controllers to make a web remote controller for a robot, i use django to host the server. When i access the ip of the Django server in firefox i get errors like: getGamepads is not a function or errors while trying to get gamepads from the navigator, but when i access through chrome this does not happen. These errors only happen while accessing through the django server, when i access through the local file or other pages in the web that use gamepad api there is no issue. Because of that i think that it has something to do with firefox tight security restrictions on http sites, but i can't find a way to grant permission to my page to work properly, i am willing to compromise in security since it's just going to be used locally

Wszystkie odpowiedzi (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

I see several dom.gamepad prefs on the about:config page, like:

  • about:config => dom.gamepad.enabled = true

This would indicate that the Gamepad API is enabled.

Noticed this bug:

  • 1337161 - Disable navigator.getGamepads() when privacy.resistFingerprinting = true [56]
  • 878828 - finalize and enable Gamepad API [28]
zeroknight
zeroknight
more options
Use mkcert to make a self-signed certificate for your internal IP address. Then add it to the list of trusted root certificates in Firefox installations on devices on your local network.

From Bug 1591329.