Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2019.3
2019.3.10f1
2020.2
Issue ID
1244514
Regression
No
[UIElements] FloatField.formatString is not applied to initial field values
Reproduction steps:
1. Open attached project "FieldFormat"
2. In Menu bar, open Window -> UIElements -> Test
3. In Test window, observe "field1" format
Expected result: The field has a decimal point
Actual result: The field does not have a decimal point
Reproducible with: 2019.3.13f1, 2020.1.0b8, 2020.2.0a11
Could not test with: 2018.4.22f1 (UIElements namespace does not exist)
Notes:
1. The proper field format is applied upon field value update, or after selecting and deselecting the field
2. Updating the field value on initialization fixes the issue.
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
- Nothing happens when entering a converter ID to target property in the Add Binding window when a converter ID was already added and removed
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- [Linux] Numeric field value stops increasing when cursor reaches the edge of the monitor while dragging
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a16