Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
1
Found in
2019.4.37f1
2020.3.32f1
2021.2.17f1
2022.1.0b14
2022.2.0a9
Issue ID
UUM-3463
Regression
No
Editor window shows incorrect layout of properties when using InspectorElement
How to reproduce:
1. Open the user's attached project
2. In the Project window, select "Inspect Me With The Window (Material)"
3. Go to Test -> Editor Window
4. Resize and lengthen the TestWindow by dragging its side to the right
5. Observe the layout of the properties
Expected result: property names align to the left column while property values align to the right column, fitting into the window
Actual result: all properties align to the right column while value fields do not entirely fit into the window
Reproducible with: 2019.4.37f1, 2020.3.32f1, 2021.2.17f1, 2022.1.0b14, 2022.2.0a9
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:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it (in this specific case, using InspectorElements in custom locations is not a specifically supported workflow). We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2022.2.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that other higher-priority issues should take precedence, and we have decided not to address your issue at this time. The priority level is determined by factors such as the severity and frequency of an issue and the number of users affected by it (in this specific case, using InspectorElements in custom locations is not a specifically supported workflow). We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.