Re: [w3c/gamepad] xbox gamepad mapped differently in firefox and chrome on Linux (#133)

This repository is more for the actual specification of the API (how it should work, what kind of information is exposed, best practices, etc.) rather than the implementation.

From a technical standpoint, the mappings should be following what's listed under [the spec](https://www.w3.org/TR/gamepad/). If the inputs aren't mapped to what's shown, then it's an issue with the browser vendor.

The problem you're having would be better posting in the bug trackers for the respective browser vendors. I've linked them below for convenience:
**Current Gamepad API bugs in Chromium** - https://bugs.chromium.org/p/chromium/issues/list?q=component%3ABlink%3EGamepadAPI&can=2
**Current Gamepad API bugs in Firefox (under the 'Device Interfaces' category)** - https://bugzilla.mozilla.org/buglist.cgi?product=Core&component=DOM%3A%20Device%20Interfaces&bug_status=__open__

@marcoscaceres Would it be possible to close this?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/133#issuecomment-636430997