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)
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
shubhamswaraj2021
Aug 21, 2020 05:56
good one <a href="https://www.lyricsauto.com">lyricsauto</a>