Search Issue Tracker
Active
Votes
0
Found in
6000.5.0a3
Issue ID
UUM-129724
Regression
Yes
UI Document does not expand in the Hierarchy if there are any pending changes in the UI Builder window
Steps to reproduce:
- Open the attached project
- Open the SampleScene
- Create a new UI Document object in the Hierarchy
- Assign the test.uxml asset to the newly created UI document object
- Observe that the UI Document object can be fully expanded to display its Visual Elements
- Open the test.uxml asset in the UI Builder window
- Make any changes to the document (for instance, add a new label element)
- Try expanding the UI Document object in the Hierarchy window again
Actual results: The UI Document object does not expand, or the expanded elements flicker for a brief moment
Expected results: The UI Document can be fully expanded
Reproducible with versions: 6000.3.0a5, 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Not reproducible with versions: 6000.3.0a3, 6000.3.0a4
Can’t test with versions: 6000.0.63f1, 6000.2.14f1, 6000.3.0a2 (UI Authoring Hierarchy integration was not yet available)
Tested on (OS): Ubuntu 24.04, macOS 26.1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [WebGPU] clearing 2d array texture only clears first slice
- Particle System Renderer icon is missing in Animation window > Add Property context menu
- [Android] Legacy, TMP and UI Toolkit Input Field language toggle to some non-latin alphabet languages does not work with external keyboard
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
Add comment