Search Issue Tracker

Won't Fix

Votes

0

Found in

6000.3.0f1

6000.4.0a5

6000.5.0a2

Issue ID

UUM-129151

Regression

No

UXML object is collapsed in the Scene Hierarchy after the file is modified

-

Steps to reproduce:

  1. Open the attached project
  2. Open the SampleScene
  3. Fully expand the UI Document object in the Scene Hierarchy
  4. Open NewUXMLTemplate.UXML file in UI Builder
  5. Make any changes to the file (for instance, change the name of one of the visual elements)
  6. Observe the UI Document in the Scene Hierarchy window

Actual results: The UI Document object is collapsed after making changes in the file

Expected results: The UI Document remains expanded

Reproducible with versions: 6000.3.0a3, 6000.3.0f1, 6000.4.0a5, 6000.5.0a2

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

Notes:

  • The project needs to use Hierarchy V2 and have UI Authoring Hierarchy integration setting enabled in the Project Settings
  1. Resolution Note:

    This feature is still experimental and under two feature flags. This is a known UX quirk that happens because when you change a value from the UI Builder, it will reload the content of the UI Document. When the content is reloaded, new instances of visual elements will be created, which will not be the same as the previous ones.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.