Search Issue Tracker
Fixed
Fixed in 2022.3.62f1, 6000.0.48f1, 6000.1.1f1, 6000.2.0a10
Votes
1
Found in
2022.3.58f1
6000.0.34f1
6000.1.0b1
6000.2.0a6
Issue ID
UUM-97892
Regression
No
Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
Reproduction steps:
1. Change the system language to "Japanese" (on Windows: "Start -> Settings -> Time & Language -> Language -> Add a language", type "Japanese", select it and press "Install")
2. Change the hardware keyboard layout to "Japanese keyboard (106/109 key)" (on Windows: "Start -> Settings -> Time & Language -> Language", select "Japanese" and press "Options", then, under "Hardware keyboard layout", press "Change layout" and change the layout to "Japanese keyboard (106/109 key)")
3. Change your input method to "Japanese" (on Windows: press the "Windows Key + Spacebar")
4. Open the attached "repro_IN-91415" project
5. Open the Build Profiles ("File -> Build Profiles")
6. Switch the platform to "Web"
7. Press the "Build & Run" button
8. Once the Player launches, open the "On-Screen Keyboard" (on Windows: "Search -> On-Screen Keyboard")
9. Press the "Backslash" button (on the "On-Screen Keyboard": button to the left of the "Backspace" button or the button to the left of the "Arrow Up" button)
10. Observe the Player
Expected result: White area at the top is updated with the pressed button information
Actual result: White area at the top is not updated with the pressed button information
Reproducible with: 2022.3.58f1, 6000.0.34f1, 6000.1.0b1
Couldn’t test with: 6000.0.35f1, 6000.0.39f1, 6000.1.0b7, 6000.2.0a4 - Bug, which is reported under UUM-97841, is blocking from testing, as the Scene is stuck in the loading screen because of it
Reproducible on: Windows 10 (22H2)
Not reproducible on: No other environments tested
Notes:
- Not reproducible in the Play Mode
- Not reproducible in the Windows Standalone Player
- Link to the UUM-97841: https://issuetracker.unity3d.com/issues/scene-from-a-specific-project-is-stuck-loading-in-the-web-player-with-the-uncaught-in-promise-typeerror-error-thrown-in-the-browser-console
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment