Search Issue Tracker
Fixed
Fixed in 2021.3.35f1, 2022.3.20f1, 2023.2.9f1, 2023.3.0b5, 7000.0.0a1
Votes
0
Found in
2023.3.0b1
Issue ID
UUM-58598
Regression
No
Unity build does not start in Chrome if running on an iframe that has the gamepad security policy disabled.
-Chrome has changed its behavior to start throwing a security exception if navigator.getGamepads() is called and the page is run from an insecure origin (without https:// URL)-
If running Unity content on an iframe that does not have gamepad security policy enabled, Chrome might throw an exception (depending on origin trial)
This exception is reported to prevent Unity web content from running.
Gamepad support landed in November 2018 by 003606e82451fa068e441d6641368a4d8a24d964 .
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment