Search Issue Tracker
Fixed in 2020.1
Fixed in 2019.3
Votes
0
Found in
2018.2
2020.1.0a8
Issue ID
1188665
Regression
Yes
[Linux] [Editor] Input Fields do not accept all Numpad numbers
How to reproduce:
1. Open the attached project 'case_number_repro.zip'
2. Make sure 'SampleScene' scene is open and enter Play mode
3. Try to enter some numbers from Numpad into the Input Fields
Expected results: All numbers are being typed in the field
Actual results: Only 0, 3, 5 and 9 are being typed in, Numpad key bindings are being called when typing other numbers or Del
Reproducible with: 2018.4.10f1, 2019.2.8f1, 2019.3.0b6, 2020.1.0a8
Not reproducible with: 2017.4.32f1
Regression was introduced somewhere in the 2018.2 stream, but before 2018.2.0b9
Notes:
- Input Field accepts only 0, 3, 5 and 9 and TMP Input Field only accepts 5 and 0, which could mean that the fields only accept Numpad numbers which do not have other bindings
- ',' symbol on the Numpad deletes the character after the cursor
- Player is not affected
- The problematic Numpad numbers behave the same way if the Numlock was off
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
- Search Sync sends wrong initial search query
- Perforce integration - Attempting to add a P4Ignore ignored file does nothing
- URP ScriptableObject SerializeField value set to default during the first Import
- Variables use old overridden values on Prefabs when a variable has FormerlySerializedAs attribute
- [GPU PLM] 100% repro crash when baking EnterTheRoom with 4K maps when using system allocator
Resolution Note (fix version 2020.1):
Fixed numeric keypad not respecting num-lock for Input Fields.
Resolution Note (fix version 2019.3):
Fixed numeric keypad not respecting num-lock for Input Fields.