Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.19f1
2023.2.7f1
2023.3.0b4
6000.0.0b11
Issue ID
UUM-62378
Regression
Yes
Inspector collapses properties when editing prefab's dropdown values
Reproduction steps:
1. Open the attached "PrefabInspectorDropdownReload.zip" project
2. Select "Assets/GameObject.prefab" to see its properties in the Inspector
3. In the “Polygon Collider 2D” Component click the “Points” dropdown (Unravel nested dropdowns if they're not visible as well)
4. Enter any number in the “Size” property (Paths>Size)
5. Press the “Enter” button on the keyboard
Expected results: The unraveled dropdowns are still visible
Actual results: Dropdowns collapse to the highest level (in these steps - to Points)
Reproducible with: 2022.3.9f1, 2022.3.19f1, 2023.2.7f1, 2023.3.0b4
Not reproducible with: 2021.3.34f1, 2022.3.8f1
Reproducible on: macOS 13.6.3 (Intel), Windows 11
Not reproducible on: no other environment tested
Note:
- Only reproducible on a prefab GameObject
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
- 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
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.