Search Issue Tracker
Duplicate
Votes
0
Found in
2021.3
2022.1.0a9
2022.2
2022.2.0a9
Issue ID
1424215
Regression
Yes
Fields are misaligned in the Inspector when they are using attributes
Reproduction steps:
1. Open the attached project "Case_1424215.zip" and load Scene "SampleScene"
2. Select the "Character" GameObject in the Hierarchy
3. Compare the fields of "Id" and "Health" under the Character Component in the Inspector
Expected result: The fields look identical
Actual result: The fields are misaligned
Reproducible with: 2021.3.3f1, 2022.1.0a9, 2022.1.2f1, 2022.2.0a15
Not reproducible with: 2022.1.0a8
Could not test with: 2019.4.39f1, 2020.3.35f1 (InspectorElement.FillDefaultInspector() not available)
Notes:
- In 2022.2.0a8 and below the issue only affected custom Editors using "InspectorElement.FillDefaultInspector()". As of 2022.2.0a9, it affects the default Editor as well
- Affects attributes such as [Min()] and [Range()]
- Example with no custom Editor can be seen in the "test" Component of the Character GameObject
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment