Open Bug 2041049 Opened 3 months ago Updated 3 months ago

Can't select specific buttons in GFN with Xbox One controller

Categories

(Core :: DOM: Device Interfaces, defect, P2)

Firefox 151
Desktop
All
defect

Tracking

()

Tracking Status
firefox151 --- affected

People

(Reporter: csasca, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: webcompat:platform-bug)

User Story

user-impact-score:400

Attachments

(1 file)

Found in

  • Firefox 151.0

Affected versions

  • Firefox 151.0

Tested platforms

  • Affected platforms: Windows 11, Ubuntu 24.04, macOS 26.5

Preconditions

  • Have a controller connected via cable or bluetooth/wireless

Steps to reproduce

  1. Access GFN
  2. Launch any game inside the browser
  3. Wait for the gaming rig to be prepared

Expected result

  • After the gaming rig is ready, a Let's go button appears and can be pressed by the controller

Actual result

  • After the gaming rig is ready, a Let's go button appears which cannot be pressed by the controller

Additional notes

  • The button can be seen in the attachment
  • After further investigations with jrmuizel, the controller may be detected differently from Chrome in Hardwaretester webpage.
  • Seems that on macOS 26.5, the controller (Xbox one) is detected as 045e-0b20-Xbox Wireless Controller, the buttons can be pressed inside the page, but it cannot be used at all in GFN (Chrome works as expected)
Component: DOM: Core & HTML → DOM: Device Interfaces

Catalin, if you click through that button does the game pad work for controlling the game?

Flags: needinfo?(csasca)

Yes, after passing by it with the mouse, the actual game menu and gameplay works as expected (so far tried on Rocket League and War Thunder).

Flags: needinfo?(csasca)

I can reproduce this.

User Story: (updated)

This issue also happens with a DualSense controller but there is a workaround it using the touchpad on the controller and it acts like a mouse so you can click on the "Let's go" button.

The button operates via the onBridgeButtonClick(). In Chrome I see it being triggered with a 'Enter' KeyboardEvent that's coming from code like _.dispatchEvent(new KeyboardEvent(y, {...e(a))

The severity field is not set for this bug.
:cmartin, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(cmartin)
Severity: -- → S3
Flags: needinfo?(cmartin)
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: