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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a16