Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0b7
2020.1.0a1
Issue ID
1190504
Regression
No
[UIElements] Non-arithmetic character "f" gets validated to zero in float, double fields
Non-arithmetic character "f" gets validated to zero in float, double fields. Refer the attached video
Steps to reproduce
1) Open attached project
2) UIE Test Suite > Open FTP
3) Controls > Open Window
4) Enter value 3.5f in float field
Actual result: Float value gets auto-validated to zero
Expected Result: Values with character "f" should be accepted in float and double fields OR "f" should be curtailed and the value "3.5" should be kept
Occurring on: 2020.1.0a8, 2019.3.0b7, 2019.2.0f1, 2019.1.9f1
Environment: Both Windows and Mac
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Given the current roadmap for UIElements this improvement will not be a priority and isn't likely to get tackled any time soon.