Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2018.4
2019.4
2019.4.21f1
2020.3
2021.1
2021.2
Issue ID
1320719
Regression
No
Input Field's width doesn't change after entering specific combinations of text when the Content Size Fitter is used
How to reproduce it:
1. Open the user's attached project "UITestProject.zip"
2. Load the "SampleScene" Scene
3. Enter the Play Mode
4. In the Game view click on the top-left Input Field
5. Write "11111" into the Input Field
Expected result: Full text ("11111") appears in the Input Field
Actual result: Only "1" appears in the Input Field
Reproducible with: 2018.4.33f1, 2019.4.22f1, 2020.3.1f1, 2021.1.0f1, 2021.2.0a10
Notes:
- Full text appears after entering a character that is different from the previous one, e.g. "123456", "111112", "122221"
- Sometimes reproducible with different characters. E.g. while entering "tex", the Input field doesn't show anything, but after writing a full "text" word, the text appears in the Input Field
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 (fix version 2022.1):
Fixed in: 2022.1.0b1