Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.1.0b10
2022.2.0a7
Issue ID
UUM-3474
Regression
No
[UI Toolkit][Mobile] Slider Input field value doesn't reset to 0 when invalid data is input
Steps to reproduce:
1. Open the attached project
2. Build to a device
3. Click the "UI Toolkit scene" button to switch scene
4. Click on the Slider input Field to activate keyboard for input
5. Type some letters or symbols (any invalid input for a float field)
6. Click "Ok" or "Done"
Expected results: Input Field value is reset to 0, same as Float Field
Actual results: The invalid string is left in the field as the value
Reproducible with: 2022.1.0b10, 2022.2.0a7
Reproduced on:
VLNQA00158 iPhone X, A11, 14.7.1
VLNQA00103, Samsung Galaxy Note8 (SM-N950F), Android 7.1.1, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
Samsung S8 (SM-G950F), Android 8.0.0, CPU: Exynos 8895 Octa, GPU: Mali-G71 MP20
Notes:
- Doesn't reproduce in Editor
- Clicking anywhere in the scene resets the value to 0
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
- Low performance when multiple meshes using BlendShape are rendered on screen
- TMP Dropdown visually corrupts or disappears when its own GameObject is assigned to "Caption Image" or "Placeholder" elements
- Usymtool tries to upload GameAssembly.pdb when it doesn't exist after building with Mono backend
- “NullReferenceException” error thrown in the Console when running HDRP Wizard “Fix All” in URP project after installing HDRP Package
- "Debug Draw Mode" unchecked checkboxes are not visible
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2022.2.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.