Search Issue Tracker
Fixed
Fixed in 6000.3.0b2, 6000.4.0a1
Votes
0
Found in
6000.3.0a5
6000.4.0a1
Issue ID
UUM-114497
Regression
No
Visual Elements cannot be enabled or disabled using Hierarchy V2
Steps to reproduce:
- Open the attached project
- Open the Test Scene
- Expand the UI document in the Hierarchy window
- Try enabling/disabling UI elementsÂ
Actual results: UI elements cannot be enabled or disabled using the Hierarchy window
Expected results: UI elements can be enabled or disabled using the Hierarchy window or if the properties can't be changed they appear as read-only
Reproducible with versions: 6000.3.0a5
Can’t test with versions: 6000.0.56f1, 6000.1.16f1, 6000.2.1f1, 6000.3.0a4 (UI Toolkit integration with Hierarchy V2 not available)
Tested on (OS): macOS 15.6, Ubuntu 24
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note (fix version 6000.3.0b2):
Visual elements are now more clearly marked as being read-only