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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment