Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.15f1
Issue ID
UUM-33308
Regression
Yes
Input field value disappears in the Inspector window when changing Input field value to 5+ characters long and using a slider next to it
Reproduction steps:
1. Open the attached “FAV_repro_IN-37735 (2022.2.0a12)” project
2. Open “Assets/Test Scene 0” Scene
4. Select the “Player” GameObject
5. Modify the “Move Speed” field of the “Player Controller (Script)” Component to “5555555555”
6. Move the slider next to the field to the left
7. Observe the “Move Speed” value text field
Expected result: The “Move Speed” value is visible
Actual result: The “Move Speed” value is invisible
Reproducible with: 2022.2.0a12, 2022.2.15f1, 2023.1.0b10, 2023.2.0a3
Not reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.0a11, 2023.1.0b12, 2023.2.0a11
Fixed in: 2023.1.0b11, 2023.2.0a4
Reproduced 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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
Bug fixed in subsequent version