Gamepad only can be shown up in a single tab when visiting to multiple Gamepad tabs.
Categories
(Core :: DOM: Device Interfaces, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox78 | --- | fixed |
People
(Reporter: daoshengmu, Assigned: daoshengmu)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
STP:
- Open a tab and visit https://html5gamepad.com/
- Press buttons or push axes to make this tab recognizes the gamepad is connected.
- Open an another tab and visit https://html5gamepad.com/
- We can find in the second tab, our gamepad can not be recognized.
I have checked FF on Windows and Mac OS. Both of them have the same result.
Assignee | ||
Updated•2 years ago
|
I am experiencing this issue after updating, I wanted to include some additional information from debugging/troubleshooting.
This issue was introduced in release 56.0.0
Disabling browser.tabs.remote.autostart
fixes the issue.
navigator.getGamepads
in the second window seems to return an empty list
Assignee | ||
Comment 2•2 years ago
|
||
(In reply to Zac from comment #1)
I am experiencing this issue after updating, I wanted to include some additional information from debugging/troubleshooting.
This issue was introduced in release 56.0.0
Disablingbrowser.tabs.remote.autostart
fixes the issue.
navigator.getGamepads
in the second window seems to return an empty list
Good to know! I guess we need to handle the case of multiple content processes.
Updated•2 years ago
|
Assignee | ||
Comment 3•8 months ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=b8dabcef05394a363e2daafc113a3c61490b4ffc try looks good now and confirmed my local patch fixes this issue. Once I am done with rebasing, we can start to review.
Assignee | ||
Comment 4•8 months ago
|
||
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Assignee | ||
Comment 5•8 months ago
•
|
||
The original issue was happened when only sending GamepadAdded events to the first GamepadEventChannel. That makes the later content processes would not have the existing gamepad objects. Therefore, I think we should send extra GamepadAdded events for the later GamepadEventChannels.
Pushed by dmu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/df539e0d6851 Send GamepadAdded events to the later GamepadEventChannels. r=baku
Comment 7•8 months ago
|
||
bugherder |
Description
•