Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.3.X
Votes
13
Found in
2019.3.0f1
2019.4
2020.2
Issue ID
1258876
Regression
No
[New Input System] Keyboard input is not detected in the Input Field when built on WebGL
How to reproduce:
1. Open user's attached "InputFieldTestProject.zip" project
2. Go to File -> Build Settings
3. Make sure the platform is set to WebGL
4. Press Build
5. Write some text in the Input Field in the browser
Expected result: Text appears in the Input Field, keyboard input (eg. CTRL+V) is registered
Actual result: No text appears in the Input Field, keyboard input (eg. CTRL+V) is not registered
Reproducible with: 0.2.10-preview (2019.4.2f1), 1.0.0 (2020.1.0b14, 2020.2.0a17)
Could not test with: 2018.4.24f1 (New Input System not supported)
Notes:
- The issue is not reproducible in the Editor and on Windows, Mac build
- The issue is not reproducible with the Old Input System
-
therobby3
Jul 23, 2020 14:54
I am having this issue as well. Also adding that related to this is the mouse scroll wheel and using ScrollRect's in game. If you use the new input system and publish to WebGL, the scroll rect will scroll extremely slow. However it will work fine in the editor.
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2020.2):
Fixed in: 2021.1.0a1
Note:
The WebGL input system has been fixed so keyboard events will be sent to GUI controls with the new input system
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.13f1