Search Issue Tracker
Fixed
Fixed in 2022.2.17f1, 2023.1.0b14, 2023.2.0a11
Votes
0
Found in
2022.2.12f1
2023.1.0b9
2023.2.0a8
Issue ID
UUM-31090
Regression
Yes
Decimal separator (, or .) gets recognized as a 0 when inserting it the first time in the input field before a number if a number has a range
How to reproduce:
1. Open the attached “slider.zip” project
2. Select “SomeSo.asset” (Assets > SomeSo)
3. In the Inspector window, focus the input field of a slider value
4. Insert “.25” or “,25”
5. Observe the result
Expected result: Value is “0.25“
Actual result: Value is “1”
Reproducible with: 2022.2.0a9, 2022.2.12f1, 2023.1.0b9, 2023.1.0a8
Not reproducible with: 2020.3.46f1, 2021.3.21f1, 2022.2.0a8
Reproduced on: macOS 13.2.1 (Intel)
Notes:
When inserting “.25” or “,25” it gets recognized as a "25" and because a number has a range of 0-1 then it gets converted to "1"
Reproducible with any numbers
Not reproducible without setting a range of a number
Not reproducible if inserting decimal separator (, or .) two times
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
- Vertex data is displaced when building with Addressables with Optimize Mesh Data enabled
- [macOS] “Input.GetMouseButtonDown” gets set to true when pressing and when releasing the mouse button in the Device Simulator view if "targetFrameRate" is set in the script
- UWP Capabilities are not changed when rebuilding the project
- [Oculus] Lights causing artifacts when Forward+ Rendering is selected
- Game Window Icons are white when in light mode
Resolution Note (fix version 2023.2.0a11):
Fixed 2023.2.X: Decimal separator (, or .) gets recognized as a 0 when inserting it the first time in the input field before a number if a number has a range
Resolution Note (fix version 2023.1.0b14):
Fixed in: 2023.1.0b14
Resolution Note (fix version 2022.2.17f1):
Fixed in: 2022.2.17f1