Not signed in
Copyright © 2026 Unity Technologies
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.
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.
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.
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.
Reproduction steps:
1. Open the attached “IN-116488_PropertyFieldBug.zip“ archived project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Select the “MyClass“ GameObject in the Hierarchy
4. Observe the Inspector
Expected result: The “Some Value” property should be expandable as the “My Property“ one
Actual result: The “Some Value“ property is not expandable and has a value assigned to it
Reproducible with: 6000.0.58f1, 6000.1.16f1, 6000.2.6f1, 6000.3.0b3
Reproducible on: M1 Max MacOS 15.5 (Tested by CQA)
Not reproducible on: No other environment tested
Note: When the Inspector is in the Debug Mode, the “Field type UnityEngine.UIElements.Foldout is not compatible with float property "someValue.someValue"“ warning is logged
Sign in to see your voted issues