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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment