Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.1.5f1
2021.2.0a5
2021.2.0a19
Issue ID
UUM-234
Regression
Yes
Linux Bug Reporter text input fields ignore Num Lock state and do not allow entering numbers using the numpad
How to reproduce:
1. Create an open a new project
2. In the menu bar open the Bug Reporter by going to: Help > Report a Bug...
3. Make sure Num Lock is enabled
4. In the Bug Reporter's "Title" text input field enter the following text (use numpad for numbers): qwerty44
Expected result: The full string was entered
Actual result: Only the "qwerty" part of the string appeared with the caret being moved left with each press of the "4" key
Reproducible with: 2021.1.5f1, 2021.2.0a5, 2021.2.0a19
Not reproducible with: 2018.4.35f1, 2019.4.28f1, 2020.3.11f1, 2021.1.0a10, 2021.2.0a4
Notes:
1. Reproducible on Ubuntu 18.04
2. Not reproducible on Windows 10
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
- 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
Resolution Note:
There are no fixes planned for this Bug