Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2018.2.0b5
Issue ID
1050364
Regression
No
Decimal type Input Field does not respect current culture
How to reproduce on Windows OS:
1. Go to Control Panel->Clock and Region->Region->Additional settings
2. Make sure that Decimal symbol is ','(comma)
3. Open user-submitted project (InputFieldBug.zip)
4. Try using comma as decimal separator
Expected result: Unity respects the current culture and uses comma as decimal separator
Actual result: Unity uses '.'(period) as decimal separator
Reproducible with: 2017.1.4p2, 2017.2.3p2, 2017.4.6f1, 2018.1.7f1, 2018.2.0b8, 2018.3.0a3
Notes:
- One can use comma while assigning InputField value in the inspector (this introduces inconsistency between InputField input validation and InputField inspector validation)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment