Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.60f1
6000.2.8f1
6000.3.0b6
6000.4.0a2
6000.5.0a1
6000.6.0a1
Issue ID
UUM-122024
Regression
No
Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
Reproduction steps:
1. Create a new project
2. Create UI Document (Create > UI Toolkit > UI Document)
3. Select newly created Asset
4. Observe the foldouts in the Inspector
Actual result: Some foldouts appear enabled even though all of the fields inside are disabled while other foldouts are disabled
Expected result: All foldouts that have all of their fields disabled are greyed out/disabled
Reproducible with: 2021.3.57f1, 2022.3.67f1, 6000.0.60f1, 6000.2.8f1, 6000.3.0b6, 6000.4.0a2
Reproduced on: Ubuntu 24.04, macOS Sequoia 15.4 (M4)
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
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.
Resolution Note (6000.6.X):
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.