Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.42f1
2022.3.43f1
6000.0.15f1
Issue ID
UUM-78459
Regression
No
Input System character mapped to key working as "By Location" in Web Builds when using AZERTY keyboard layout
How to reproduce:
1. Open attached “InputSystemWebGL.zip” project
2. Switch keyboard layout to AZERTY
3. In Play Mode press either the Q or Z key according to AZERTY layout
4. Observe the result (nothing happens)
5. Build and run the project using WebGL
6. In the built project press either the Q or Z key according to AZERTY layout
7. Observe the result
Expected result: The square does not move when Q or Z keys are pressed in the built project
Actual result: Q and Z key presses are registered as A and W, moving the square
Reproducible in: 2021.3.42f1, 2022.3.43f1, 6000.0.15f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Physical AZERTY keyboard not required, changing layout in OS settings is enough to reproduce
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
- Look Dev window flickers when resizing the window after docking it
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.