Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.45f1
2021.3.19f1
2022.2.7f1
2023.1.0b3
2023.2.0a2
Issue ID
UUM-27035
Regression
No
FoldoutHeaderGroup cannot be expanded or collapsed when in DisabledGroup
Reproduction steps:
1. Open the “FoldoutHeaderGroup“ project
2. Open the “SampleScene” scene
3. Select the “CustomInspectorTest“ GameObject
4. In Inspector try to expand and collapse the “Foldout Header Group - does not work when disabled” foldout
Expected result: the foldout can be expanded and collapsed
Actual result: the foldout cannot be expanded or collapsed
Reproduced in: 2020.3.45f1, 2021.3.19f1, 2022.2.7f1, 2023.1.0b3, 2023.2.0a2
Reproduced using: macOS 13.0.1 (Intel), Windows 11 (by reporter)
Notes:
1. Also reproduced when expanding materials at the bottom of Inspector (sub-foldouts cannot be expanded/collapsed)
2. Not reproduced with regular `EditorGUILayout.Foldout`
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 this issue is not aligned with our current development priorities and focus areas (UI Toolkit). As such, we have decided not to invest time and resources into addressing it. 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 (2023.2.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas (UI Toolkit). As such, we have decided not to invest time and resources into addressing it. 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.