Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3.0b2
2019.3.0b7
2020.1
Issue ID
1194487
Regression
Yes
Inspector Property field text alignments are inconsistent
Reproduction steps:
1. Open the attached project "1194487"
2. In the Hierarchy, select "Main Camera"
Expected result: All Property field texts are aligned the same
Actual result: The Property field text alignments are different (screenshots attached)
Reproducible with: 2019.3.0b2, 2019.3.0b9, 2020.1.0a11
Not reproducible with: 2017.4.34f1, 2018.4.12f1, 2019.2.11f1, 2019.3.0b1
Note: Alignment became different when the default text font was changed by Unity (difference shown in the attached screenshots)
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 (2020.1.X):
This would require too much effort for the actual gain. This will be automatically fixed when we will upgrade the inspector to UIE as flex will do a much better job than IMGUI layout.